Triple
T11053618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Battle of Lissa |
E261317
|
entity |
| Predicate | AustrianFleetOutcome |
P97531
|
FINISHED |
| Object | victory |
—
|
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: victory | Statement: [Naval Battle of Lissa, AustrianFleetOutcome, victory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AustrianFleetOutcome Context triple: [Naval Battle of Lissa, AustrianFleetOutcome, victory]
-
A.
AustrianGunsLost
Indicates that certain guns or artillery pieces belonging to Austrian forces were lost.
-
B.
AustrianCasualtiesApprox
Indicates an approximate number or estimate of casualties suffered by Austrian forces or entities.
-
C.
combatantCommanderAustria
Indicates that the referenced entity served as a military commander for Austria in a particular conflict or combat situation.
-
D.
involvedUnitAustriaHungary
Indicates that the unit or force specified was involved on behalf of Austria-Hungary in the referenced event or conflict.
-
E.
strengthRussoAustrian
Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7986d49e0819096c9e96b2ea1b38b |
completed | April 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.