Triple
T8368240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hòa Bình Province |
E197387
|
entity |
| Predicate | localEthnicLanguage |
P10892
|
FINISHED |
| Object | Mường language |
—
|
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: Mường language | Statement: [Hòa Bình Province, localEthnicLanguage, Mường language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localEthnicLanguage Context triple: [Hòa Bình Province, localEthnicLanguage, Mường language]
-
A.
ethnicLanguageStatus
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
-
B.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
C.
regionLanguage
chosen
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
D.
localLanguageName
Indicates the name of a language as it is written or referred to in its own local or native form.
-
E.
ethnoLinguisticRegionOf
Indicates that a region is defined or characterized by the shared ethnic and linguistic identity of the group associated with it.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808e56fc81908b5d37482f29452d |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:01 p.m.