Triple
T4271558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proto-Turkic |
E96950
|
entity |
| Predicate | hasSubgroupSplit |
P11294
|
FINISHED |
| Object | Common Turkic vs Oghur Turkic |
—
|
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: Common Turkic vs Oghur Turkic | Statement: [Proto-Turkic, hasSubgroupSplit, Common Turkic vs Oghur Turkic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubgroupSplit Context triple: [Proto-Turkic, hasSubgroupSplit, Common Turkic vs Oghur Turkic]
-
A.
haveSubgroups
Indicates that an entity is organized into smaller constituent groups that are part of it.
-
B.
hasSplit
chosen
Indicates that an entity has undergone a division into two or more distinct parts, groups, or components.
-
C.
hasSubfieldGroup
Indicates that an entity includes or is associated with a specific subgroup of related subfields within its overall structure or domain.
-
D.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
-
E.
hasSubspace
Indicates that one space is a subset or component of another, existing entirely within the larger space.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ffce3d8819083d2278547fa52c1 |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.