Triple
T4080630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States nuclear weapons testing |
E87467
|
entity |
| Predicate | haltedBy |
P41870
|
FINISHED |
| Object | 1992 U.S. nuclear testing moratorium |
—
|
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: 1992 U.S. nuclear testing moratorium | Statement: [United States nuclear weapons testing, haltedBy, 1992 U.S. nuclear testing moratorium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haltedBy Context triple: [United States nuclear weapons testing, haltedBy, 1992 U.S. nuclear testing moratorium]
-
A.
halted
chosen
Indicates that an ongoing process, action, or movement has been stopped or brought to an end.
-
B.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
-
C.
heldOver
Indicates that something has been continued, carried forward, or extended in effect or duration beyond its original or expected time.
-
D.
heldAfter
Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
-
E.
held
Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc5204d881909829de15015aa50d |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.