Triple
T11217917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triomphant-class ballistic missile submarines |
E265484
|
entity |
| Predicate | nuclearPropulsion |
P36733
|
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: [Triomphant-class ballistic missile submarines, nuclearPropulsion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearPropulsion Context triple: [Triomphant-class ballistic missile submarines, nuclearPropulsion, true]
-
A.
nuclearPowered
chosen
Indicates that something operates using nuclear energy as its primary power source.
-
B.
thermalNeutronReactor
Indicates that the subject is a nuclear reactor that operates using thermal (low-energy) neutrons to sustain its fission chain reaction.
-
C.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
D.
usedOnNuclearPoweredVessel
Indicates that something is employed or operated aboard a vessel that is powered by nuclear energy.
-
E.
propulsionFeature
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ea19e8819095d5d02c1f145534 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.