Triple

T14523492
Position Surface form Disambiguated ID Type / Status
Subject Bulozi Plain E340710 entity
Predicate roleInKuomboka P114589 FINISHED
Object route of Litunga’s annual move between palaces LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: route of Litunga’s annual move between palaces | Statement: [Bulozi Plain, roleInKuomboka, route of Litunga’s annual move between palaces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInKuomboka
Context triple: [Bulozi Plain, roleInKuomboka, route of Litunga’s annual move between palaces]
  • A. roleInBabel
    Indicates that an entity participates in the Babel project or system with a specific role or function.
  • B. roleInCoco
    Indicates that an entity serves a specific role or function within the context of the COCO dataset or framework.
  • C. roleInvolves
    Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
  • D. roleInGemini10
    Indicates that an entity holds a specific role or position in the context of the Gemini 10 mission or project.
  • E. roleInBun
    Indicates that an entity has a specific functional or contextual role within a particular bundle, grouping, or composite structure.
  • F. None of above. chosen

Provenance (4 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69d822dac79c8190a84a073f3cbaced5 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dea04f16f88190ba357b0f8021b46b completed April 14, 2026, 8:15 p.m.
PD Predicate disambiguation batch_69de5c518fc08190a6ce4d8be05c4c5d completed April 14, 2026, 3:25 p.m.
PDg Predicate description generation batch_69de5fb5ac548190932f238e37271741 completed April 14, 2026, 3:39 p.m.
Created at: April 10, 2026, 1:22 a.m.