Triple

T16466966
Position Surface form Disambiguated ID Type / Status
Subject King of Babylon E399957 entity
Predicate positionHeldBy P8 FINISHED
Object Kandalanu E355268 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: Kandalanu | Statement: [King of Babylon, positionHeldBy, Kandalanu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kandalanu
Context triple: [King of Babylon, positionHeldBy, Kandalanu]
  • A. Kandalanu chosen
    Kandalanu was a late 7th-century BC king of Babylon, likely installed as a vassal ruler under the Assyrian Empire before the rise of Nabopolassar and the Neo-Babylonian dynasty.
  • B. Kandan
    Kandan is a locality within Beijing’s Fengtai District, known primarily as a residential and urban neighborhood area.
  • C. Kalkan
    Kalkan is a picturesque seaside town on Turkey’s Mediterranean coast, known for its historic architecture, steep cobbled streets, and upscale tourism.
  • D. Kankanay
    Kankanay is an Austronesian language spoken by the Kankanaey people of the northern Philippines, particularly in the Cordillera region of Luzon.
  • E. Cansilayan
    Cansilayan is a barangay (village-level administrative division) within the municipality of Oton in the province of Iloilo, Philippines.
  • 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_69d87f2dac988190b74d6e185fa88ba4 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32dcd707081908fb7ca91a8c09e0a completed April 18, 2026, 7:07 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004f575ed48190a24d6af74565189d completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 5:11 a.m.