Triple
T25265332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sinking of Patria |
E633413
|
entity |
| Predicate | deportationDestinationPlanned |
P26248
|
FINISHED |
| Object | Mauritius |
E28590
|
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: Mauritius | Statement: [sinking of Patria, deportationDestinationPlanned, Mauritius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deportationDestinationPlanned Context triple: [sinking of Patria, deportationDestinationPlanned, Mauritius]
-
A.
mainDeportationDestination
chosen
Indicates the primary location to which individuals are deported in a given deportation event or process.
-
B.
deportedTo
Indicates that an authority forcibly removed a person from one place or country and sent them to another specified destination.
-
C.
deportedBy
Indicates that an entity was expelled or removed from a country or territory by a specific authority, agent, or organization.
-
D.
deportedFrom
Indicates that an authority has expelled an entity from a particular place or country, forcing their departure from that location.
-
E.
deportedOn
Indicates that an authority forcibly removed a person from a country or territory on a specific date or at a specific time.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4839787908190a5fc04739139cee8 |
completed | May 1, 2026, 10:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a118f73fc0c8190b3f20df8499e8704 |
completed | May 23, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:14 p.m.