Triple
T31970237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MR-UR-100 |
E816291
|
entity |
| Predicate | nuclearWeapon |
P173488
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [MR-UR-100, nuclearWeapon, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nuclearWeapon Context triple: [MR-UR-100, nuclearWeapon, true]
-
A.
nuclearWeaponsProgram
Indicates the existence, development, or pursuit of a program related to the research, production, or maintenance of nuclear weapons.
-
B.
nuclearWeaponDesign
Indicates that an entity is involved in the creation, specification, or technical configuration of a nuclear weapon.
-
C.
nuclearPowered
Indicates that something operates using nuclear energy as its primary power source.
-
D.
nuclearExplosiveType
Indicates the specific category or kind of nuclear explosive device associated with an entity or event.
-
E.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:10 a.m.