Triple
T32212144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khaling Rai |
E822835
|
entity |
| Predicate | linguisticAutonym |
P1435
|
FINISHED |
| Object | Khaling |
—
|
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: Khaling | Statement: [Khaling Rai, linguisticAutonym, Khaling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linguisticAutonym Context triple: [Khaling Rai, linguisticAutonym, Khaling]
-
A.
autonymLanguageFamily
Indicates that a language’s self-designated name (autonym) belongs to or is classified within a particular language family.
-
B.
linguisticIdentity
Indicates that two or more entities share, express, or are characterized by the same language or linguistic affiliation.
-
C.
isEndonym
Indicates that a name is used by a group to refer to themselves or their own place/language, rather than being an external or foreign designation.
-
D.
hasEndonym
chosen
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
E.
autonymLanguageCode
Indicates that the associated language code is the one used by a language to refer to itself (its autonym).
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:37 a.m.