Triple
T31937988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhahti Kue |
E815442
|
entity |
| Predicate | hasIndigenousToponymStatus |
P191080
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zhahti Kue, hasIndigenousToponymStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndigenousToponymStatus Context triple: [Zhahti Kue, hasIndigenousToponymStatus, true]
-
A.
hasIndigenousToponymy
chosen
Indicates that a place or geographic feature bears a name originating from an Indigenous language or naming tradition.
-
B.
toponymStatus
Indicates the status or classification of a place name within a geographic naming or toponymic system.
-
C.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
D.
hasToponymicUse
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
-
E.
hasEthnolinguisticOriginOfToponym
Indicates that a toponym (place name) originates from or is derived from a particular ethnolinguistic group or language.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 1, 2026, 12:05 a.m.