Triple
T32581066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essex-class aircraft carrier |
E832784
|
entity |
| Predicate | someShipsReclassifiedAs |
P123188
|
FINISHED |
| Object | attack aircraft carrier (CVA) |
—
|
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: attack aircraft carrier (CVA) | Statement: [Essex-class aircraft carrier, someShipsReclassifiedAs, attack aircraft carrier (CVA)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: someShipsReclassifiedAs Context triple: [Essex-class aircraft carrier, someShipsReclassifiedAs, attack aircraft carrier (CVA)]
-
A.
renamedShipAs
Indicates that one entity changed the name of a ship to another specified name.
-
B.
shipClassDeveloped
Indicates that a particular ship class was developed or designed by a specified entity (such as a country, organization, or manufacturer).
-
C.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
D.
shipsUsedAs
chosen
Indicates that certain ships are employed or repurposed to serve in a specified role, function, or capacity.
-
E.
fleetOrClass
Indicates that something belongs to, is part of, or is categorized under a particular fleet or class.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c669d6408190bc26dbf21f59e237 |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.