Triple

T13450738
Position Surface form Disambiguated ID Type / Status
Subject Tabal region E320599 entity
Predicate relatedTo P37 FINISHED
Object Kummuh E753017 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: Kummuh | Statement: [Tabal region, relatedTo, Kummuh]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kummuh
Context triple: [Tabal region, relatedTo, Kummuh]
  • A. Kummuh chosen
    Kummuh was an Iron Age Neo-Hittite kingdom located in southeastern Anatolia, known from Assyrian records as a regional political and cultural center.
  • B. King Yan
    King Yan is a deity in Chinese mythology who presides over the underworld and judges the souls of the dead.
  • C. King Sinmun
    King Sinmun was a monarch of the Korean kingdom of Silla who played a key role in consolidating and governing the peninsula after its unification in the late 7th century.
  • D. King Gwanggaeto the Great
    King Gwanggaeto the Great was a renowned 5th-century Korean monarch who vastly expanded the territory and power of the Goguryeo kingdom, making it one of the dominant states in East Asia.
  • E. King Sanna
    King Sanna was an early Javanese ruler known from ancient inscriptions as a predecessor in the lineage that led to the rise of the Mataram Kingdom in Central Java.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaef973b08190a3d7fe1c2a913cff completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f73999f8388190b2c578e063341178 completed May 3, 2026, 12:03 p.m.
Created at: April 9, 2026, 9:41 p.m.