Triple
T18284813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 17 thermonuclear bomb |
E437954
|
entity |
| Predicate | armsControlStatus |
P131180
|
FINISHED |
| Object | retired |
—
|
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: retired | Statement: [Mark 17 thermonuclear bomb, armsControlStatus, retired]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armsControlStatus Context triple: [Mark 17 thermonuclear bomb, armsControlStatus, retired]
-
A.
armsControl
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.
armsControlSignificance
Indicates the extent to which an action, event, or agreement has importance or impact within the context of arms control efforts and policies.
-
D.
armamentStatus
Indicates the current condition or readiness level of an entity’s weapons or military equipment.
-
E.
weaponControl
Indicates that one entity has authority over, access to, or the ability to direct the use of a weapon associated with another entity.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500f913d48190b41a1e37ca05e8b1 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a0ba208190a5fe92832a8f7a49 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:35 a.m.