Triple
T36582749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Vis (1866) |
E902437
|
entity |
| Predicate | ItalianFlagship |
P185896
|
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), ItalianFlagship, Re d’Italia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ItalianFlagship Context triple: [Battle of Vis (1866), ItalianFlagship, Re d’Italia]
-
A.
alignedItalyWith
Indicates that one entity brought Italy into political, military, or ideological agreement or cooperation with another entity.
-
B.
ItalyFormation
Indicates the event or process by which Italy was established or formed as a unified or distinct political entity.
-
C.
ItalianObjective
Indicates that an entity has an objective, goal, or target specifically related to Italy or the Italian context.
-
D.
ItalianComponent
Indicates that something is a component, element, or part that is specifically Italian in origin, style, or association.
-
E.
ItalianVersionClaimed
Indicates that an entity asserts or is reported to have an Italian-language version.
- 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_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.