Triple
T22050186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangut |
E544861
|
entity |
| Predicate | hasUnicodeBlock |
P1445
|
FINISHED |
| Object | Tangut |
—
|
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: Tangut | Statement: [Tangut, hasUnicodeBlock, Tangut]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tangut Context triple: [Tangut, hasUnicodeBlock, Tangut]
-
A.
Tangut
chosen
Tangut is an extinct Tibeto-Burman language once used in the Western Xia dynasty, best known today for its large and complex logographic writing system.
-
B.
Tangut people
The Tangut people were a Tibeto-Burman ethnic group of northwestern China who founded and ruled the Western Xia dynasty until its destruction by the Mongol Empire.
-
C.
Dholuo
Dholuo is a Nilotic language spoken primarily by the Luo people of western Kenya and parts of Tanzania.
-
D.
Chochenyo
Chochenyo is an indigenous Ohlone language traditionally spoken in the East Bay region of the San Francisco Bay Area in California.
-
E.
Tangut script
The Tangut script is a complex, logographic writing system historically used by the Tangut people of the Western Xia dynasty in northwestern China.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128323fb08190b9592fd08a96cba0 |
completed | April 28, 2026, 9:35 p.m. |
Created at: April 16, 2026, 8:26 p.m.