Triple
T7761685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Pope |
E176035
|
entity |
| Predicate | crewStatusAfterLoss |
P24303
|
FINISHED |
| Object | most of crew survived sinking |
—
|
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: most of crew survived sinking | Statement: [USS Pope, crewStatusAfterLoss, most of crew survived sinking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewStatusAfterLoss Context triple: [USS Pope, crewStatusAfterLoss, most of crew survived sinking]
-
A.
crewStatus
Indicates the current operational or role-related condition of a crew member or crew group within a mission or organization.
-
B.
crewComplementAtSinking
Indicates the number or composition of a vessel’s crew present on board at the time it sank.
-
C.
crewFatality
Indicates that one or more members of a crew have died as a result of the related event or situation.
-
D.
crewSurvivorsOnReturn
chosen
Indicates that the members of a crew remained alive and successfully returned from a mission or journey.
-
E.
crewOnReturn
Indicates that a crew member is assigned to be on board a specific vehicle, mission, or vessel for its return journey.
- 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_69c69962923c8190ac74d28b4f9fe0a0 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:09 p.m.