Triple
T30048720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngmayem |
E763531
|
entity |
| Predicate | associatedEthnicSubgroup |
P45393
|
FINISHED |
| Object | Shai-Osudoku |
E1691322
|
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: Shai-Osudoku | Statement: [Ngmayem, associatedEthnicSubgroup, Shai-Osudoku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedEthnicSubgroup Context triple: [Ngmayem, associatedEthnicSubgroup, Shai-Osudoku]
-
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.
containedEthnicGroup
chosen
Indicates that one entity (typically a larger group, region, or population) includes or encompasses a particular ethnic group within it.
-
C.
involvedEthnicGroup
Indicates that a particular ethnic group participates in, is affected by, or is otherwise associated with the referenced event, situation, or entity.
-
D.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
-
E.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a273241e628819091f2c6bf46e46304 |
completed | June 8, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 6:54 p.m.