Triple
T11005649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CC-1 |
E260110
|
entity |
| Predicate | redesignatedShipType |
P21289
|
FINISHED |
| Object | aircraft carrier |
—
|
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: aircraft carrier | Statement: [CC-1, redesignatedShipType, aircraft carrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redesignatedShipType Context triple: [CC-1, redesignatedShipType, aircraft carrier]
-
A.
renamedShipAs
Indicates that one entity changed the name of a ship to another specified name.
-
B.
originalShipType
Indicates the type or category of ship that an entity was originally classified or built as.
-
C.
secondShipRenamedAs
Indicates that a second ship has been given a new name, establishing a renaming relationship between its prior and current identities.
-
D.
conversionOfShip
chosen
Indicates the process by which a ship is altered or transformed from one configuration, role, or specification into another.
-
E.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797562de4819097a0e136180d283a |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.