Triple
T31472013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegis Combat System |
E802884
|
entity |
| Predicate | laterShipClassIntegrated |
P199619
|
FINISHED |
| Object | Arleigh Burke-class destroyer |
—
|
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: Arleigh Burke-class destroyer | Statement: [Aegis Combat System, laterShipClassIntegrated, Arleigh Burke-class destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterShipClassIntegrated Context triple: [Aegis Combat System, laterShipClassIntegrated, Arleigh Burke-class destroyer]
-
A.
laterShipType
Indicates that one ship type chronologically succeeds or is introduced after another ship type.
-
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.
primaryAlliedCruiser
Indicates that one entity serves as the main or principal allied cruiser associated with another entity.
-
E.
previousShipClass
Indicates that one ship class directly precedes another in a sequence or lineage of ship classes.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
| PDg | Predicate description generation | batch_69ff490096388190832a90e9abbc8d81 |
completed | May 9, 2026, 2:47 p.m. |
Created at: April 30, 2026, 9:26 p.m.