Triple
T31507407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trident successor programme |
E803854
|
entity |
| Predicate | nuclearArmament |
P17998
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Trident successor programme, nuclearArmament, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearArmament Context triple: [Trident successor programme, nuclearArmament, yes]
-
A.
nuclearArsenalStatus
Indicates the condition or level of development, deployment, or readiness of an entity’s nuclear weapons capability.
-
B.
nuclearWeaponsState
Indicates that a state possesses, has developed, or is recognized as having nuclear weapons capabilities.
-
C.
nuclearDeterrentLeg
Indicates a legal or policy measure that contributes to a state's nuclear deterrent posture or capability.
-
D.
nuclearCapability
Indicates that an entity possesses, develops, or has access to nuclear weapons or the technological capacity to produce them.
-
E.
nuclearWeaponsProgram
chosen
Indicates the existence, development, or pursuit of a program related to the research, production, or maintenance of nuclear weapons.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 9:48 p.m.