Triple
T35715196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyain Seikgyi |
E1031983
|
entity |
| Predicate | hasCommonLocalEthnicGroup |
P207108
|
FINISHED |
| Object | Kayin (Karen) people |
E1763857
|
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: Kayin (Karen) people | Statement: [Kyain Seikgyi, hasCommonLocalEthnicGroup, Kayin (Karen) people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonLocalEthnicGroup Context triple: [Kyain Seikgyi, hasCommonLocalEthnicGroup, Kayin (Karen) people]
-
A.
hasCommonEthnicGroup
Indicates that two entities share at least one ethnic group in common.
-
B.
commonInEthnicGroup
Indicates that something (such as a trait, condition, or characteristic) occurs with notable frequency within a specified ethnic group.
-
C.
mayBelongToEthnicGroup
Indicates that an entity is possibly, but not certainly, a member of a specified ethnic group.
-
D.
nearEthnicGroup
Indicates that one entity is located geographically close to an ethnic group.
-
E.
hasEthnicGroupType
Indicates that an entity is associated with, characterized by, or classified according to a particular type or category of ethnic group.
- F. None of above. chosen
Provenance (5 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3885e94af88190919eb1f2952914df |
completed | June 22, 2026, 12:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:05 p.m.