Triple
T3736872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohingya |
E79605
|
entity |
| Predicate | 2017ExodusScale |
P51365
|
FINISHED |
| Object | hundreds of thousands fled to Bangladesh |
—
|
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: hundreds of thousands fled to Bangladesh | Statement: [Rohingya, 2017ExodusScale, hundreds of thousands fled to Bangladesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2017ExodusScale Context triple: [Rohingya, 2017ExodusScale, hundreds of thousands fled to Bangladesh]
-
A.
exileStart
Indicates the point in time or event when an entity begins being forced to live away from its home or native place.
-
B.
exileEnd
Indicates the point or event at which a period of exile for an entity comes to an end.
-
C.
periodOfExile
Indicates a time span during which an entity is banished, expelled, or forced to live away from its native or rightful place.
-
D.
exportedVia
Indicates that something is sent out or made available to an external destination through a specified medium, channel, or mechanism.
-
E.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
- F. None of above. chosen
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_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. |
| PDg | Predicate description generation | batch_69adc45debe48190b1c1f894e02b0316 |
completed | March 8, 2026, 6:47 p.m. |
Created at: March 8, 2026, 3:34 p.m.