Triple
T31472037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegis Combat System |
E802884
|
entity |
| Predicate | AegisAshoreRole |
P171919
|
FINISHED |
| Object | land-based ballistic missile defense |
—
|
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: land-based ballistic missile defense | Statement: [Aegis Combat System, AegisAshoreRole, land-based ballistic missile defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AegisAshoreRole Context triple: [Aegis Combat System, AegisAshoreRole, land-based ballistic missile defense]
-
A.
navalEngagementRole
Indicates the specific function or duty an entity performs within a naval engagement or maritime combat operation.
-
B.
navalTacticRole
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
-
C.
hasNavalRole
Indicates that an entity holds or is assigned a role, function, or duty within a naval or maritime context.
-
D.
roleInUSCG
Indicates that one entity holds or held a specific role, position, or duty within the United States Coast Guard in relation to the other entity.
-
E.
coastRole
Indicates a role or function that an entity has specifically in relation to a coast or coastal area.
- 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_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 9:26 p.m.