Triple
T25820471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Columbia (SSBN-826) |
E650387
|
entity |
| Predicate | submarineClassRole |
P159309
|
FINISHED |
| Object | ballistic missile submarine (SSBN) |
—
|
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: ballistic missile submarine (SSBN) | Statement: [USS Columbia (SSBN-826), submarineClassRole, ballistic missile submarine (SSBN)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: submarineClassRole Context triple: [USS Columbia (SSBN-826), submarineClassRole, ballistic missile submarine (SSBN)]
-
A.
submarineClassLeadShip
Indicates that one entity is the lead (first-built or first-commissioned) ship of a particular submarine class represented by the other entity.
-
B.
primarySubmarineClassSupported
Indicates that an entity is designed to support, service, or operate primarily with a specific class of submarines.
-
C.
submarine
Indicates that one entity is a submarine in relation to another entity or context.
-
D.
navalTacticRole
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
-
E.
propulsionRole
Indicates the specific function or responsibility an entity has within a propulsion system or propulsion-related process.
- 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_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. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 7:29 a.m.