Triple
T7743439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umpiem Mai refugee camp |
E175564
|
entity |
| Predicate | reasonForDisplacement |
P3057
|
FINISHED |
| Object | armed conflict in Myanmar |
—
|
LITERAL 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: armed conflict in Myanmar | Statement: [Umpiem Mai refugee camp, reasonForDisplacement, armed conflict in Myanmar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDisplacement Context triple: [Umpiem Mai refugee camp, reasonForDisplacement, armed conflict in Myanmar]
-
A.
reasonForRelocation
chosen
Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location to another.
-
B.
displacementCause
Indicates a causal relationship where one entity is responsible for the displacement or forced movement of another entity from its original location or situation.
-
C.
displacedBy
Indicates that one entity has been moved, replaced, or forced out of its original position, role, or state by another entity.
-
D.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
-
E.
plannedDisplacement
Indicates a deliberate, pre-arranged movement or relocation of an entity from one place or state to another.
- 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_69c6995f9c60819092e386192bd63c6f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:07 p.m.