Triple
T35959152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Milwaukee |
E1039948
|
entity |
| Predicate | crewAndPassengersFatalities |
P33471
|
FINISHED |
| Object | all hands lost |
—
|
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: all hands lost | Statement: [SS Milwaukee, crewAndPassengersFatalities, all hands lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewAndPassengersFatalities Context triple: [SS Milwaukee, crewAndPassengersFatalities, all hands lost]
-
A.
fatalitiesOnboard
chosen
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
-
B.
crewFatality
Indicates that one or more members of a crew have died as a result of the related event or situation.
-
C.
coPassengerInFatalCrashWith
Indicates that two or more individuals were passengers in the same vehicle involved in a fatal crash.
-
D.
causedFatalities
Indicates that the referenced event or action directly resulted in one or more deaths.
-
E.
casualtiesHijackers
Indicates that the hijackers caused or were responsible for casualties (deaths or injuries) among others.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.