Triple

T20931296
Position Surface form Disambiguated ID Type / Status
Subject Siyavash E515476 entity
Predicate nameVariant P744 FINISHED
Object Siyâvaš 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: Siyâvaš | Statement: [Siyavash, nameVariant, Siyâvaš]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Siyâvaš
Context triple: [Siyavash, nameVariant, Siyâvaš]
  • A. Siyāvash
    Siyāvash is a tragic prince in the Persian epic Shahnameh, renowned for his innocence, sense of justice, and unjust martyrdom.
  • B. Pishva
    Pishva is a city in Tehran Province, Iran, known as an administrative and local commercial center for the surrounding region.
  • C. Siyavash chosen
    Siyavash is a tragic prince and hero in the Persian epic Shahnameh, renowned for his innocence, loyalty, and unjust death.
  • D. Savena
    Savena is a river in northern Italy that flows through the Emilia-Romagna region, including the area near Bologna.
  • E. Dārayamūš
    Dārayamūš is the Akkadian form of the name Darius, used in ancient Mesopotamian texts to refer to the Achaemenid Persian kings bearing that name.
  • 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_69e6f6557e4881909ce932c3f538304a completed April 21, 2026, 4 a.m.
Created at: April 16, 2026, 12:49 p.m.