Triple
T25820473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Columbia (SSBN-826) |
E650387
|
entity |
| Predicate | ballisticMissileCapability |
P46288
|
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 Columbia (SSBN-826), ballisticMissileCapability, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballisticMissileCapability Context triple: [USS Columbia (SSBN-826), ballisticMissileCapability, true]
-
A.
missileLaunchCapability
Indicates that an entity has the ability or functionality to launch missiles.
-
B.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
-
C.
hasBallisticMissileSubmarine
chosen
Indicates that an entity possesses or operates a submarine specifically designed to carry and launch ballistic missiles.
-
D.
missileFamily
Indicates that one missile belongs to, or is categorized within, the same family or series as another missile.
-
E.
missileRange
Indicates the maximum distance over which a missile can effectively travel to reach and engage a target.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f601909ea481909674a1438dede725 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:29 a.m.