Triple
T20956863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyage of the Winnipeg |
E516123
|
entity |
| Predicate | numberOfRefugeesTransported |
P23315
|
FINISHED |
| Object | over 2,000 |
—
|
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: over 2,000 | Statement: [Voyage of the Winnipeg, numberOfRefugeesTransported, over 2,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfRefugeesTransported Context triple: [Voyage of the Winnipeg, numberOfRefugeesTransported, over 2,000]
-
A.
approximateNumberOfRefugeesTransported
chosen
Indicates an estimated count of refugees who were transported in the described event or context.
-
B.
hasRefugeeMovements
Indicates that there are movements or flows of refugees involving the related entities, such as people fleeing from one place and arriving in another.
-
C.
carriedImmigrantsTo
Indicates that one entity transported immigrants from one place to another.
-
D.
hasRefugeePopulation
Indicates that an entity hosts, contains, or is associated with a population of refugees.
-
E.
refugeeTransportIncident
Indicates an incident or event involving the transportation of refugees, such as movement, transfer, or conveyance under specific circumstances.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6c2f1481908360fb86d2b6a8e4 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:28 p.m.