Triple
T31224085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavour-class aircraft carrier |
E796089
|
entity |
| Predicate | homeportOfLeadShip |
P96373
|
FINISHED |
| Object | Taranto |
—
|
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: Taranto | Statement: [Cavour-class aircraft carrier, homeportOfLeadShip, Taranto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeportOfLeadShip Context triple: [Cavour-class aircraft carrier, homeportOfLeadShip, Taranto]
-
A.
homeportAsNOAA
Indicates that a vessel’s designated home port is assigned or recognized specifically as a NOAA (National Oceanic and Atmospheric Administration) home port.
-
B.
homeportDuringWar
Indicates that an entity served as the designated home port or primary base for another entity during a period of war.
-
C.
homeportCity
chosen
Indicates the city that serves as the primary home port or base location for a vessel or similar entity.
-
D.
homeportCountry
Indicates the country where a vessel is officially registered as its home port.
-
E.
hasResearchVesselsHomeport
Indicates that a location serves as the primary homeport or base of operations for one or more research vessels.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c5030b88190bac4667e104238af |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.