Triple
T32916513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Brien McMahon |
E842025
|
entity |
| Predicate | ballisticMissileSubmarine |
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 Brien McMahon, ballisticMissileSubmarine, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballisticMissileSubmarine Context triple: [USS Brien McMahon, ballisticMissileSubmarine, true]
-
A.
hasBallisticMissileSubmarine
chosen
Indicates that an entity possesses or operates a submarine specifically designed to carry and launch ballistic missiles.
-
B.
submarine
Indicates that one entity is a submarine in relation to another entity or context.
-
C.
submarineClassLeadShip
Indicates that one entity is the lead (first-built or first-commissioned) ship of a particular submarine class represented by the other entity.
-
D.
submarineClassName
Indicates the specific class designation or type category to which a submarine belongs.
-
E.
notableMissile
Indicates that the subject is a missile distinguished by particular significance, prominence, or noteworthiness (e.g., historical impact, technological importance, or public attention).
- 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_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:19 a.m.