Triple
T2023342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trident nuclear missile system |
E44152
|
entity |
| Predicate | armsControlContext |
P31885
|
FINISHED |
| Object | subject to US-UK nuclear cooperation agreements |
—
|
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: subject to US-UK nuclear cooperation agreements | Statement: [Trident nuclear missile system, armsControlContext, subject to US-UK nuclear cooperation agreements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armsControlContext Context triple: [Trident nuclear missile system, armsControlContext, subject to US-UK nuclear cooperation agreements]
-
A.
armsControl
chosen
Indicates a relationship where parties engage in limiting, regulating, or reducing weapons and military capabilities, often through agreements or treaties.
-
B.
hasArm
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
-
C.
armType
Indicates the specific kind or configuration of an arm associated with an entity.
-
D.
hasArms
Indicates that an entity possesses arms as physical appendages.
-
E.
robotControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the actions and behaviors of one or more robots.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f1728481909ae36e821b9edef2 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.