Triple
T37633744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manus Regional Processing Centre |
E936423
|
entity |
| Predicate | finalDetaineeTransferCompleted |
P85515
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Manus Regional Processing Centre, finalDetaineeTransferCompleted, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalDetaineeTransferCompleted Context triple: [Manus Regional Processing Centre, finalDetaineeTransferCompleted, 2019]
-
A.
detentionOutcome
Indicates the result or consequence of a detention, such as whether it was continued, ended, or changed in status.
-
B.
transferCompletedOn
chosen
Indicates that a transfer action has been fully completed at or by a specific point in time.
-
C.
finalCessionBy
Indicates that one party makes the last or conclusive transfer or assignment of rights, claims, or property to another party.
-
D.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
-
E.
detainedAfter
Indicates that one entity is held in custody or confinement following another specified event or action.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 3, 2026, 4:18 p.m.