Triple
T31224081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavour-class aircraft carrier |
E796089
|
entity |
| Predicate | serviceEntryOfLeadShip |
P157877
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [Cavour-class aircraft carrier, serviceEntryOfLeadShip, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEntryOfLeadShip Context triple: [Cavour-class aircraft carrier, serviceEntryOfLeadShip, 2009]
-
A.
statusOfLeadShip
Indicates the current condition or state assigned to the primary or leading ship in a given context or operation.
-
B.
shipManager
Indicates a relationship where one entity manages, oversees, or is responsible for the operation and administration of a ship.
-
C.
classLeadShip
Indicates a leadership relationship where one entity serves as the leading or primary representative of a class, group, or category.
-
D.
serviceEntryNavy
chosen
Indicates the point at which an entity begins or has begun official service in a navy.
-
E.
leadShip
Indicates that one entity serves as the commander or person in charge of a ship belonging to or associated with another entity.
- 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_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 9:10 p.m.