Triple
T31224791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold War-era Royal Navy |
E796108
|
entity |
| Predicate | nuclearDeterrentPlatform |
P47242
|
FINISHED |
| Object | Resolution-class submarine |
—
|
NE NERFINISHED |
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: Resolution-class submarine | Statement: [Cold War-era Royal Navy, nuclearDeterrentPlatform, Resolution-class submarine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearDeterrentPlatform Context triple: [Cold War-era Royal Navy, nuclearDeterrentPlatform, Resolution-class submarine]
-
A.
nuclearDeterrentLeg
Indicates a legal or policy measure that contributes to a state's nuclear deterrent posture or capability.
-
B.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
-
C.
nuclearPowered
Indicates that something operates using nuclear energy as its primary power source.
-
D.
nuclearWeaponsCustodian
Indicates that one entity is responsible for the control, safekeeping, or management of another entity’s nuclear weapons.
-
E.
nuclearWarheadCarrier
chosen
Indicates that an entity is designed or used to carry, transport, or deliver nuclear warheads.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c5030b88190bac4667e104238af |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.