Triple

T33261319
Position Surface form Disambiguated ID Type / Status
Subject Alakul culture E851519 entity
Predicate hasLanguageFamilyHypothesis P138721 FINISHED
Object Indo-Iranian 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: Indo-Iranian | Statement: [Alakul culture, hasLanguageFamilyHypothesis, Indo-Iranian]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLanguageFamilyHypothesis
Context triple: [Alakul culture, hasLanguageFamilyHypothesis, Indo-Iranian]
  • A. languageFamilyHypotheses chosen
    Indicates proposed or theorized genealogical relationships among languages, grouping them into potential common families or macro-families.
  • B. basedOnLanguageFamily
    Indicates that one entity is derived from, structured according to, or otherwise determined by the language family to which another entity belongs.
  • C. coversLanguageFamily
    Indicates that one entity includes or encompasses a particular language family within its scope or subject matter.
  • D. hasLanguageFamilyHigher
    Indicates that one language family is hierarchically higher or more encompassing than another language family in a classification structure.
  • E. inLanguageFamily
    Indicates that two languages belong to the same linguistic family or classification.
  • 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_69f349642dac81908a37ffcc3b976a55 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fed83b1d188190a318b0ad3003200a completed May 9, 2026, 6:46 a.m.
PD Predicate disambiguation batch_69fed78e03548190b6e6ad93ae8d131d completed May 9, 2026, 6:43 a.m.
Created at: May 1, 2026, 1:31 a.m.