Triple
T29230343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tay |
E741048
|
entity |
| Predicate | legalStatusInVietnam |
P175290
|
FINISHED |
| Object | officially recognized ethnic minority |
—
|
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: officially recognized ethnic minority | Statement: [Tay, legalStatusInVietnam, officially recognized ethnic minority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInVietnam Context triple: [Tay, legalStatusInVietnam, officially recognized ethnic minority]
-
A.
statusInVietnam
chosen
Indicates the legal, social, or official standing or condition an entity holds specifically within the context of Vietnam.
-
B.
legalStatusInChina
Indicates the legal status or standing that an entity holds under the laws and regulations of China.
-
C.
legalStatusOfPhilippines
Indicates the legal or political status that the Philippines holds in relation to another governing authority or international framework.
-
D.
legalStatusInTaiwan
Indicates the legal status or recognition that an entity has within the jurisdiction of Taiwan.
-
E.
legalStatusInMyanmar
Indicates the legal status or standing that an entity holds under the laws and regulations of Myanmar.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 28, 2026, 12:18 p.m.