Triple

T13561832
Position Surface form Disambiguated ID Type / Status
Subject Yatta Plateau E323926 entity
Predicate nearbySettlement P350 FINISHED
Object Voi E320476 NE 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: Voi | Statement: [Yatta Plateau, nearbySettlement, Voi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Voi
Context triple: [Yatta Plateau, nearbySettlement, Voi]
  • A. Voi chosen
    Voi is a town in southeastern Kenya that serves as a key gateway and service hub for visitors to Tsavo National Park.
  • B. Viiala
    Viiala was a former municipality in southern Finland that later became part of the town of Akaa.
  • C. Vitsa
    Vitsa is a traditional stone-built village in the Zagori region of Epirus, northwestern Greece, known for its preserved architecture and scenic mountain setting.
  • D. Ogna
    Ogna is a river in Trøndelag county, Norway, known for flowing through the municipality of Steinkjer.
  • E. Veleti
    The Veleti were a confederation of early medieval West Slavic tribes inhabiting the southern Baltic coast, known for their resistance to neighboring powers such as the early Polish state and the Holy Roman Empire.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d8076830b48190910a902bae5888e2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaff5219081909cf60423e79d278f completed April 12, 2026, 2:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75dad601481908de5f266f01f3f49 completed May 3, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:47 p.m.