Triple
T35049412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Albacore (SS-218) |
E1011286
|
entity |
| Predicate | crewLost |
P29707
|
FINISHED |
| Object | all hands |
—
|
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 | Statement: [USS Albacore (SS-218), crewLost, all hands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewLost Context triple: [USS Albacore (SS-218), crewLost, all hands]
-
A.
crewFatality
chosen
Indicates that one or more members of a crew have died as a result of the related event or situation.
-
B.
hullLoss
Indicates that an aircraft has suffered damage or destruction severe enough to be considered a total loss of the airframe.
-
C.
fatalitiesOnboard
Indicates that the relationship specifies the number of people who died among those present on a particular vehicle or craft.
-
D.
shipLostWith
Indicates that one entity was lost together with another entity in the same maritime incident or disappearance.
-
E.
crewComplementAtSinking
Indicates the number or composition of a vessel’s crew present on board at the time it sank.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f785ca8fa4819088713fd7a58fa229 |
completed | May 3, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.