Triple
T31264525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oirats |
E797215
|
entity |
| Predicate | demographicSuccessor |
P62943
|
FINISHED |
| Object | Kalmyks |
—
|
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: Kalmyks | Statement: [Oirats, demographicSuccessor, Kalmyks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demographicSuccessor Context triple: [Oirats, demographicSuccessor, Kalmyks]
-
A.
successorPopulation
Indicates that one population directly follows or replaces another population in a temporal or sequential order.
-
B.
ethnicSuccessor
chosen
Indicates that one ethnic group is the successor or continuation of another, typically inheriting its identity, culture, or population in a historical or social sense.
-
C.
successorFamily
Indicates that one family succeeds or follows another family in a lineage, role, position, or ownership.
-
D.
possibleSuccessorPeoples
Indicates that one group of people is a potential successor or replacement for another group in a given context or role.
-
E.
predecessorPopulation
Indicates that one population entity is the immediate prior version or state of another population entity in a temporal or evolutionary sequence.
- 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_69f224de2bbc819081af6c32e1d857b9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:12 p.m.