Triple
T30769643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meung Yum |
E783478
|
entity |
| Predicate | relatedEthnolinguisticGroup |
P46225
|
FINISHED |
| Object | Waic peoples |
E1932457
|
NE 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: Waic peoples | Statement: [Meung Yum, relatedEthnolinguisticGroup, Waic peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEthnolinguisticGroup Context triple: [Meung Yum, relatedEthnolinguisticGroup, Waic peoples]
-
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.
ethnolinguisticGroups
chosen
Indicates a relationship where groups are categorized or associated based on shared ethnic and linguistic characteristics.
-
C.
relatedEthnonymNote
Indicates that there is an explanatory note describing how this ethnonym is related to another ethnonym or term.
-
D.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
-
E.
ethnolinguisticCluster
Indicates a relationship where entities are grouped together based on shared ethnic and linguistic characteristics, treating them as part of the same ethnolinguistic cluster.
- F. None of above.
Provenance (4 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a035052a47081908e9e56e21c543d46 |
completed | May 12, 2026, 4:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a29181518b48190a378c7984235a05a |
completed | June 10, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_6a034d306e588190a2dce906fd46eb54 |
completed | May 12, 2026, 3:54 p.m. |
Created at: April 29, 2026, 8:40 p.m.