Triple

T3330264
Position Surface form Disambiguated ID Type / Status
Subject Neriglissar E70015 entity
Predicate spouse P13 FINISHED
Object Kashshaya E347398 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: Kashshaya | Statement: [Neriglissar, spouse, Kashshaya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kashshaya
Context triple: [Neriglissar, spouse, Kashshaya]
  • A. Kashshaya chosen
    Kashshaya was a Neo-Babylonian royal woman known primarily as the wife of King Amel-Marduk.
  • B. Khashuri
    Khashuri is a town in central Georgia that serves as an important regional transport hub and gateway between eastern and western parts of the country.
  • C. Yakhin
    Yakhin is a variant form of the biblical name Jachin, traditionally associated with one of the two pillars of Solomon’s Temple.
  • D. Krakhuna
    Krakhuna is a Georgian white grape variety from the Imereti region, known for producing aromatic, full-bodied wines with pronounced acidity.
  • E. Huvishka
    Huvishka was a prominent Kushan emperor of the 2nd century CE, known for his extensive coinage and role in consolidating the empire’s power and cultural diversity across Central and South Asia.
  • 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_69ad85a24f208190bcf83131bfed3521 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb171ee0881908642504ab0ac8329 completed March 8, 2026, 5:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69b31a810e2c8190bfc206bdeb1ac5b8 completed March 12, 2026, 7:56 p.m.
Created at: March 8, 2026, 3:12 p.m.