Triple
T12796188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian battleship Vittorio Veneto |
E305894
|
entity |
| Predicate | battleResultAtCapeMatapan |
P19109
|
FINISHED |
| Object | heavily damaged but not sunk |
—
|
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: heavily damaged but not sunk | Statement: [Italian battleship Vittorio Veneto, battleResultAtCapeMatapan, heavily damaged but not sunk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleResultAtCapeMatapan Context triple: [Italian battleship Vittorio Veneto, battleResultAtCapeMatapan, heavily damaged but not sunk]
-
A.
opponentAtSurigaoStrait
Indicates that one entity was the opposing force of another in the Battle of Surigao Strait.
-
B.
battleWasPartOf
Indicates that a specific battle occurred as a component or phase within a larger military campaign, war, or conflict.
-
C.
resultOfBattle
chosen
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
-
D.
fateAtTobruk
Indicates the outcome or ultimate fate that befell an entity specifically in connection with the events at Tobruk.
-
E.
outcomeForHuáscar
Indicates the resulting fate, consequence, or end state experienced by Huáscar as a result of preceding events or actions.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6db68481909a2ca8da1287f3e0 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.