Triple
T36582750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Vis (1866) |
E902437
|
entity |
| Predicate | ItalianIronclad |
P186052
|
FINISHED |
| Object | Re d’Italia |
—
|
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: Re d’Italia | Statement: [Battle of Vis (1866), ItalianIronclad, Re d’Italia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ItalianIronclad Context triple: [Battle of Vis (1866), ItalianIronclad, Re d’Italia]
-
A.
ItalianFlagship
Indicates that an entity serves as a primary or leading representative (flagship) of Italy or Italian interests in a given domain.
-
B.
ItalianFleetOutcome
Indicates the result or consequence experienced by the Italian fleet in a particular event or engagement.
-
C.
opponentInBattleOfTheRiverPlate
Indicates that two entities were opposing sides facing each other in the Battle of the River Plate.
-
D.
AustroHungarianShipInvolved
Indicates that a ship belonging to or operated by the Austro-Hungarian Empire was involved in a specified event or interaction.
-
E.
Bravio delle Botti
Indicates a relationship involving participation in, association with, or occurrence during the Bravio delle Botti barrel-racing event.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.