Triple
T26526097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talaing |
E670691
|
entity |
| Predicate | notPreferredEndonymOf |
P133828
|
FINISHED |
| Object | Mon people |
—
|
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: Mon people | Statement: [Talaing, notPreferredEndonymOf, Mon people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notPreferredEndonymOf Context triple: [Talaing, notPreferredEndonymOf, Mon people]
-
A.
isNonEndonymFor
chosen
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.
-
B.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
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.
hasEndonymLanguage
Indicates that the language specified is the one in which a name or term is expressed in its own native or local form.
-
E.
notOfficialLanguageOf
Indicates that a language is explicitly not recognized or designated as an official language of a given entity (such as a country, region, or organization).
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613c628008190b4676558dcf17d65 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:31 a.m.