Triple
T24085658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Plum Point Bend |
E596635
|
entity |
| Predicate | UnionShipDamaged |
P155028
|
FINISHED |
| Object | USS Cincinnati |
—
|
NE NERFINISHED |
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: USS Cincinnati | Statement: [Battle of Plum Point Bend, UnionShipDamaged, USS Cincinnati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UnionShipDamaged Context triple: [Battle of Plum Point Bend, UnionShipDamaged, USS Cincinnati]
-
A.
battleshipsDamaged
Indicates that one or more battleships have sustained damage, typically as a result of combat or hostile action.
-
B.
burnedShip
Indicates that one entity intentionally set fire to and burned a ship belonging to or associated with another entity.
-
C.
wasSunkAs
Indicates that an entity met its end by being sunk in a specified role, context, or capacity.
-
D.
shipAttacked
Indicates that one ship has carried out an attack against another ship.
-
E.
sankOnMaidenVoyage
Indicates that the subject vessel sank during its very first voyage.
- F. None of above. chosen
Provenance (4 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc28a7cc81909c76d9d992ac21dc |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 10:44 p.m.