Triple
T31472012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegis Combat System |
E802884
|
entity |
| Predicate | firstShipClassIntegrated |
P207433
|
FINISHED |
| Object | Ticonderoga-class cruiser |
E1001819
|
NE 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: Ticonderoga-class cruiser | Statement: [Aegis Combat System, firstShipClassIntegrated, Ticonderoga-class cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstShipClassIntegrated Context triple: [Aegis Combat System, firstShipClassIntegrated, Ticonderoga-class cruiser]
-
A.
laterShipClassIntegrated
Indicates that a later ship class was incorporated into, or made compatible with, an earlier ship class or system.
-
B.
firstShip
Indicates that the subject is the earliest or initial ship associated with, created by, or used in relation to the object.
-
C.
shipClassDeveloped
Indicates that a particular ship class was developed or designed by a specified entity (such as a country, organization, or manufacturer).
-
D.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
E.
primaryAlliedCruiser
Indicates that one entity serves as the main or principal allied cruiser associated with another entity.
- F. None of above. chosen
Provenance (5 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_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b079551388190af2cc9b70740cc5a |
completed | June 11, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 9:26 p.m.