Triple
T33106895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nassau-class battleship |
E847211
|
entity |
| Predicate | allShipsFate |
P24302
|
FINISHED |
| Object | survived World War I |
—
|
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: survived World War I | Statement: [Nassau-class battleship, allShipsFate, survived World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allShipsFate Context triple: [Nassau-class battleship, allShipsFate, survived World War I]
-
A.
dispositionOfShips
Indicates the arrangement, allocation, or positioning of ships relative to a plan, location, or situation.
-
B.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
C.
survivingShipsOfFleet
chosen
Indicates the subset of ships from a given fleet that remain operational or undestroyed after a specific event or period.
-
D.
allShipsNamed
Indicates that all entities in the referenced set are ships that share the specified name.
-
E.
fateOfComponentShip
Indicates the outcome or final status that befalls a component of a ship within the described context or event.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6e7c0248190a5eed4c5bcf83aad |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.