Triple

T8460753
Position Surface form Disambiguated ID Type / Status
Subject Haldi E200031 entity
Predicate languageOfName P15 FINISHED
Object Urartian E200030 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: Urartian | Statement: [Haldi, languageOfName, Urartian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Urartian
Context triple: [Haldi, languageOfName, Urartian]
  • A. Urartian language chosen
    The Urartian language was an extinct agglutinative language of the ancient Near East, spoken in the kingdom centered around Lake Van in the early first millennium BCE and related to Hurrian.
  • B. Urartian cuneiform
    Urartian cuneiform is an ancient script, adapted from Neo-Assyrian cuneiform, used to write the language of the Iron Age kingdom of Urartu in the Armenian Highlands.
  • C. Hurro-Urartian
    Hurro-Urartian is a proposed ancient language family that groups together the Hurrian and Urartian languages once spoken in the Near East.
  • D. Elamite
    Elamite is an ancient language of southwestern Iran, historically used in the kingdom of Elam and later as an administrative language under the Achaemenid Empire.
  • E. Urartian period
    The Urartian period was an Iron Age era in the Near East marked by the rise of the Kingdom of Urartu, known for its fortified cities, advanced irrigation systems, and distinctive art and architecture around Lake Van.
  • 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_69ca83198c4c8190a337bf717d1813f5 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe49fca788190a8728ff74f4d26f5 completed March 31, 2026, 3:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce88bc6b008190a93fbd41089d6c72 completed April 2, 2026, 3:18 p.m.
Created at: March 30, 2026, 6:10 p.m.