Triple

T28919159
Position Surface form Disambiguated ID Type / Status
Subject Hyrcania E733458 entity
Predicate languageFamilyHistorical P22184 FINISHED
Object Iranian languages 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: Iranian languages | Statement: [Hyrcania, languageFamilyHistorical, Iranian languages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: languageFamilyHistorical
Context triple: [Hyrcania, languageFamilyHistorical, Iranian languages]
  • A. ancientLanguageFamily
    Indicates that one language belongs to or descends from a historically ancient family of related languages.
  • B. languageFamilyBranchOf
    Indicates that one language family branch is a sub-group or subdivision within a larger language family.
  • C. historicalLanguageGroup chosen
    Indicates that two or more entities belong to the same historically defined language group or family, based on shared linguistic ancestry or development.
  • D. basedOnLanguageFamily
    Indicates that one entity is derived from, structured according to, or otherwise determined by the language family to which another entity belongs.
  • E. historicalLanguageOfBearers
    Indicates that the specified language is historically spoken or used by the bearers of a given name, title, or designation.
  • F. None of above.

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_69f05b0a5cc0819094828367ae204b70 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69fe610e1f6881908f10070ba64643cf completed May 8, 2026, 10:17 p.m.
PD Predicate disambiguation batch_69fe604c6c008190ad659e9b9fa82f7b completed May 8, 2026, 10:14 p.m.
Created at: April 28, 2026, 8:18 a.m.