Triple
T1946277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkic world |
E42061
|
entity |
| Predicate | hasMainCriterion |
P7594
|
FINISHED |
| Object | use of Turkic languages |
—
|
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: use of Turkic languages | Statement: [Turkic world, hasMainCriterion, use of Turkic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainCriterion Context triple: [Turkic world, hasMainCriterion, use of Turkic languages]
-
A.
hasCriterionType
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
-
B.
hasMainReferent
Indicates that one entity serves as the primary or central referent for another entity within a given context.
-
C.
hasMainPeriod
Indicates that something is associated with or characterized by a primary or most significant time period.
-
D.
hasMainOrgan
Indicates that an entity possesses a primary or principal organ that plays a central role in its biological or functional system.
-
E.
primaryCriterion
chosen
Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
- 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb32ebae881908f7541301f0198ae |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.