Triple
T3736871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohingya |
E79605
|
entity |
| Predicate | 2017ExodusTriggeredBy |
P23268
|
FINISHED |
| Object | Myanmar military operations in Rakhine State |
—
|
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: Myanmar military operations in Rakhine State | Statement: [Rohingya, 2017ExodusTriggeredBy, Myanmar military operations in Rakhine State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2017ExodusTriggeredBy Context triple: [Rohingya, 2017ExodusTriggeredBy, Myanmar military operations in Rakhine State]
-
A.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
exileStart
chosen
Indicates the point in time or event when an entity begins being forced to live away from its home or native place.
-
C.
timeOfRevelation
Indicates the specific time or moment at which something is revealed or disclosed.
-
D.
expulsionStart
Indicates the point in time when an expulsion process or event begins.
-
E.
eschatologicalEvent
Indicates an event associated with ultimate destiny or final outcomes in a religious or philosophical end-times framework.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3d32b081909a993a78b0869db8 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.