Triple

T20931683
Position Surface form Disambiguated ID Type / Status
Subject Hushang E515485 entity
Predicate predecessor P97 FINISHED
Object Kayumars NE NERFINISHED

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: Kayumars | Statement: [Hushang, predecessor, Kayumars]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kayumars
Context triple: [Hushang, predecessor, Kayumars]
  • A. Keyumars chosen
    Keyumars is a legendary primordial king in Iranian mythology, often regarded as the first human and the first ruler in ancient Persian epic tradition.
  • B. Behram
    Behram is an alternative name for the ancient Greek city of Assos, a historic coastal settlement in present-day Turkey known for its classical ruins and scenic Aegean setting.
  • C. Faravahar
    Faravahar is one of the best-known symbols of Zoroastrianism, typically depicting a winged human figure that represents the human soul, divine protection, and moral guidance.
  • D. Hormazd
    Hormazd is an alternative name for Ahura Mazda, the supreme creator god and central deity of Zoroastrianism.
  • E. Khusrav
    Khusrav is a masculine given name of Persian origin, historically borne by princes and notable figures in Central and South Asia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4fb431c8190b9d40e6a72f0cc87 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6f65681b4819083c7ef6b44ba4bdb completed April 21, 2026, 4 a.m.
Created at: April 16, 2026, 12:49 p.m.