Triple
T35715360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papun |
E1031988
|
entity |
| Predicate | locatedInEthnicState |
P78864
|
FINISHED |
| Object | Kayin State |
E316915
|
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 State | Statement: [Papun, locatedInEthnicState, Kayin State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInEthnicState Context triple: [Papun, locatedInEthnicState, Kayin State]
-
A.
isInEthnicState
chosen
Indicates that an entity exists within or is governed by a political state defined primarily by a specific ethnic group.
-
B.
isLocatedInMajorityEthnicRegion
Indicates that an entity is situated within a geographic region where a particular ethnic group constitutes the majority of the population.
-
C.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
D.
ethnicGroupLocatedIn
Indicates that a particular ethnic group is present, resides, or is primarily associated with a specific geographic location or region.
-
E.
containedEthnicGroup
Indicates that one entity (typically a larger group, region, or population) includes or encompasses a particular ethnic group within it.
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38b6e3da6881909b46a21c3c54c1da |
completed | June 22, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.