Triple
T2101595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkic languages |
E37102
|
entity |
| Predicate | areOfficialLanguageFamilyOf |
P35817
|
FINISHED |
| Object | several sovereign states |
—
|
LITERAL 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: several sovereign states | Statement: [Turkic languages, areOfficialLanguageFamilyOf, several sovereign states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areOfficialLanguageFamilyOf Context triple: [Turkic languages, areOfficialLanguageFamilyOf, several sovereign states]
-
A.
languageFamilyBranchOf
Indicates that one language family branch is a sub-group or subdivision within a larger language family.
-
B.
languageOfFamily
Indicates the language or languages commonly used or associated with a particular family.
-
C.
influencedLanguageFamily
Indicates that one language family has had a significant impact on the development, structure, or usage of another language family.
-
D.
derivedFromLanguageFamily
Indicates that one language originates from, or historically descends from, a particular language family.
-
E.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
- F. None of above. chosen
Provenance (4 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabc83a8819091f786f21d33b5a6 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb9ce3ff08190a9501f8bb821c01c |
completed | March 7, 2026, 5:38 a.m. |
Created at: March 4, 2026, 7:43 p.m.