Triple
T32916521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Brien McMahon |
E842025
|
entity |
| Predicate | strategicWeaponsPlatform |
P161978
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [USS Brien McMahon, strategicWeaponsPlatform, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategicWeaponsPlatform Context triple: [USS Brien McMahon, strategicWeaponsPlatform, true]
-
A.
nuclearWarheadCarrier
Indicates that an entity is designed or used to carry, transport, or deliver nuclear warheads.
-
B.
isStrategicWeapon
Indicates that the weapon is designed or classified for large-scale, long-range, or high-impact strategic use rather than for tactical or localized operations.
-
C.
armamentAsCarrier
chosen
Indicates that one entity serves as a carrier or delivery platform for another entity used as an armament or weapon.
-
D.
notableMissile
Indicates that the subject is a missile distinguished by particular significance, prominence, or noteworthiness (e.g., historical impact, technological importance, or public attention).
-
E.
missileFamily
Indicates that one missile belongs to, or is categorized within, the same family or series as another missile.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:19 a.m.