Triple
T25265331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sinking of Patria |
E633413
|
entity |
| Predicate | shipPurposeAtTime |
P15346
|
FINISHED |
| Object | deportation transport |
—
|
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: deportation transport | Statement: [sinking of Patria, shipPurposeAtTime, deportation transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipPurposeAtTime Context triple: [sinking of Patria, shipPurposeAtTime, deportation transport]
-
A.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
B.
fleetPurpose
Indicates the primary function, role, or intended use of a fleet within a given context.
-
C.
purposeOfVoyages
chosen
Indicates the intended goals, reasons, or objectives motivating or justifying specific voyages.
-
D.
shipsUsedAs
Indicates that certain ships are employed or repurposed to serve in a specified role, function, or capacity.
-
E.
usedForShips
Indicates that something is designed, intended, or suitable to be used for ships or ship-related purposes.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4839787908190a5fc04739139cee8 |
completed | May 1, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:14 p.m.