Triple
T22851751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wajin |
E566371
|
entity |
| Predicate | exonymOrEndonym |
P17110
|
FINISHED |
| Object | exonym |
—
|
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: exonym | Statement: [Wajin, exonymOrEndonym, exonym]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exonymOrEndonym Context triple: [Wajin, exonymOrEndonym, exonym]
-
A.
hasExonym
Indicates that one entity is known by an alternative name or designation in another language or cultural context.
-
B.
exonymStatus
chosen
Indicates the status or classification of a name used in one language to refer to a place, people, or entity known by a different name in its own language.
-
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
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
E.
isNonEndonymFor
Indicates that a given name for a place, people, or language is used by outsiders and is not the name used by the group or locale itself.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb9a5b8819091cbb4ac42fbf778 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.