Triple
T32899559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumandin Turkic |
E841570
|
entity |
| Predicate | ethnicGroupPopulation |
P159087
|
FINISHED |
| Object | Kumandin people |
—
|
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: Kumandin people | Statement: [Kumandin Turkic, ethnicGroupPopulation, Kumandin people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicGroupPopulation Context triple: [Kumandin Turkic, ethnicGroupPopulation, Kumandin people]
-
A.
ethnicGroupCountApprox
Indicates an approximate count of distinct ethnic groups associated with or present in a given entity.
-
B.
ethnicGroupSize
Indicates the number of individuals belonging to a particular ethnic group within a specified population or context.
-
C.
populationEthnicGroup
chosen
Indicates that a specified ethnic group constitutes part or all of the population of a given place or community.
-
D.
keyPopulation
Indicates that the referenced entity belongs to a specific key population group that is of particular importance or priority in a given context (e.g., public health, policy, or services).
-
E.
ethnolinguisticGroupSize
Indicates the number of individuals belonging to a particular ethnolinguistic group.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:19 a.m.