Triple
T15202643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuman Confederation |
E363305
|
entity |
| Predicate | language |
P15
|
FINISHED |
| Object | Cuman language |
E841565
|
NE 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: Cuman language | Statement: [Cuman Confederation, language, Cuman language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cuman language Context triple: [Cuman Confederation, language, Cuman language]
-
A.
Cuman language
chosen
Cuman language is an extinct Kipchak Turkic language once spoken by the nomadic Cuman people across the Eurasian steppe in the Middle Ages.
-
B.
Kuman language
The Kuman language is a Trans–New Guinea language spoken primarily by the Chimbu (Simbu) people of Papua New Guinea’s highlands.
-
C.
Kumzari language
The Kumzari language is an endangered Southwestern Iranian language spoken primarily by the Kumzari people in the Musandam Peninsula of Oman.
-
D.
Kumandin language
The Kumandin language is a Turkic language spoken by the Kumandin people of the Altai region in Russia, belonging to the Kipchak branch.
-
E.
Rumsen language
Rumsen language is an extinct Ohlone (Costanoan) Native American language formerly spoken in the Monterey Bay area of California.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b693a48190a6230b7b52bc8cd3 |
completed | April 15, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fed3390b708190b10c876c437c72c8 |
completed | May 9, 2026, 6:24 a.m. |
Created at: April 10, 2026, 3:10 a.m.