Triple
T33117053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chorasmia |
E847484
|
entity |
| Predicate | laterLanguageGroupsSpoken |
P201054
|
FINISHED |
| Object | 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: Turkic languages | Statement: [Chorasmia, laterLanguageGroupsSpoken, Turkic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterLanguageGroupsSpoken Context triple: [Chorasmia, laterLanguageGroupsSpoken, Turkic languages]
-
A.
languageGroupSpoken
Indicates that a particular language group is spoken or used for communication by an entity.
-
B.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
C.
includesLanguagesSpokenAlong
Indicates that something (such as a region, route, or area) encompasses or contains the set of languages spoken along its extent or within its boundaries.
-
D.
languageBranchOfDialectSpoken
Indicates that one language branch is the higher-level linguistic group from which a given spoken dialect originates or to which that dialect belongs.
-
E.
includesLanguagesSpokenBy
Indicates that one entity contains or covers the set of languages spoken by another entity.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffc516d1908190b475f5a6156b0ca8 |
completed | May 9, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69ffc4a946e08190b3535a5dc15ac484 |
completed | May 9, 2026, 11:35 p.m. |
| PDg | Predicate description generation | batch_69ffc515e4b08190810b2a29b2885162 |
completed | May 9, 2026, 11:36 p.m. |
Created at: May 1, 2026, 1:27 a.m.