Triple
T30584095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | တႆး |
E778457
|
entity |
| Predicate | refersToEthnicGroupAlsoIn |
P45393
|
FINISHED |
| Object | Southeast Asia |
—
|
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: Southeast Asia | Statement: [တႆး, refersToEthnicGroupAlsoIn, Southeast Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToEthnicGroupAlsoIn Context triple: [တႆး, refersToEthnicGroupAlsoIn, Southeast Asia]
-
A.
relatedEthnicGroup
Indicates that there is a notable ethnic connection or association between two ethnic groups, such as shared ancestry, culture, or historical ties.
-
B.
commonInEthnicGroup
Indicates that something (such as a trait, condition, or characteristic) occurs with notable frequency within a specified ethnic group.
-
C.
containedEthnicGroup
chosen
Indicates that one entity (typically a larger group, region, or population) includes or encompasses a particular ethnic group within it.
-
D.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
-
E.
involvedEthnicGroup
Indicates that a particular ethnic group participates in, is affected by, or is otherwise associated with the referenced event, situation, or entity.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 29, 2026, 8:23 p.m.