Triple
T2118236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuclear weapons policy of the United Kingdom |
E43856
|
entity |
| Predicate | airDeliveredNuclearWeapons |
P34919
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Nuclear weapons policy of the United Kingdom, airDeliveredNuclearWeapons, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airDeliveredNuclearWeapons Context triple: [Nuclear weapons policy of the United Kingdom, airDeliveredNuclearWeapons, false]
-
A.
hasNuclearWeapons
Indicates that the subject possesses or controls nuclear weapons.
-
B.
nuclearWeaponsState
Indicates that a state possesses, has developed, or is recognized as having nuclear weapons capabilities.
-
C.
positionOnNuclearWeapons
Indicates a stance, policy, or viewpoint that an entity holds regarding the development, possession, use, or regulation of nuclear weapons.
-
D.
nuclearWeaponsProgram
Indicates the existence, development, or pursuit of a program related to the research, production, or maintenance of nuclear weapons.
-
E.
bombTonnageDropped
Indicates the total weight of bombs that were released or deployed in a given event or context.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb3117c081908c5e748a869d1f9f |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:44 p.m.