Triple

T5488622
Position Surface form Disambiguated ID Type / Status
Subject Avestan language E123645 entity
Predicate sacredText P1184 FINISHED
Object Yasna E403504 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: Yasna | Statement: [Avestan language, sacredText, Yasna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yasna
Context triple: [Avestan language, sacredText, Yasna]
  • A. Yasna chosen
    Yasna is a central Zoroastrian liturgical ceremony and its associated collection of sacred texts, forming one of the core sections of the Avesta.
  • B. Sadras
    Sadras is a historic coastal town in Tamil Nadu, India, known for its Dutch-era fort and role as a former trading port on the Coromandel Coast.
  • C. Hawiyah
    Hawiyah is an Islamic eschatological term referring to a deep abyss of Hell reserved for those whose evil deeds outweigh their good.
  • D. Hormuzd
    Hormuzd is a masculine given name most notably borne by Hormuzd Rassam, a 19th-century Assyriologist and archaeologist known for his discoveries of ancient Mesopotamian artifacts.
  • E. Parsa
    Parsa is the ancient name of the Persian people and their homeland, from which the ethnonym "Persian" is historically derived.
  • 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_69bd464a2d908190869324ce176779c8 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd9264d014819097c83bb5c2bb8c39 completed March 20, 2026, 6:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf48ac6e7881908806f88056409b41 completed March 22, 2026, 1:41 a.m.
Created at: March 20, 2026, 2:10 p.m.