Triple

T18987713
Position Surface form Disambiguated ID Type / Status
Subject Anahita E464598 entity
Predicate epithet P743 FINISHED
Object Anahid 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: Anahid | Statement: [Anahita, epithet, Anahid]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Anahid
Context triple: [Anahita, epithet, Anahid]
  • A. Anoush
    Anoush is a renowned Armenian opera by composer Armen Tigranian, based on Hovhannes Tumanyan’s poem and celebrated for its lyrical portrayal of rural Armenian life and tragic love.
  • B. Roshanak
    Roshanak is an ancient Persian female given name, often associated with Roxana, the wife of Alexander the Great.
  • C. Anahita chosen
    Anahita is an ancient Iranian goddess associated with water, fertility, and protection, widely venerated in the Achaemenid and later Persian empires.
  • D. Farahnaz
    Farahnaz is a Persian female given name, notably borne by Farahnaz Pahlavi, the eldest daughter of the former Shah of Iran, Mohammad Reza Pahlavi.
  • E. Roxanna
    Roxanna is a feminine given name of Persian origin, commonly interpreted to mean "dawn" or "bright."
  • 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_69d8dd008af48190a97ff1c6488edf1b completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6618ab881909c0ed94930e42e68 completed April 20, 2026, 7:31 a.m.
Created at: April 10, 2026, 12:01 p.m.