Triple
T16939642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peaceful Nuclear Explosions Treaty |
E410916
|
entity |
| Predicate | limitOnYield |
P91382
|
FINISHED |
| Object | 150 kilotons for individual explosions |
—
|
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: 150 kilotons for individual explosions | Statement: [Peaceful Nuclear Explosions Treaty, limitOnYield, 150 kilotons for individual explosions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitOnYield Context triple: [Peaceful Nuclear Explosions Treaty, limitOnYield, 150 kilotons for individual explosions]
-
A.
limitaCon
Indicates that one entity imposes a restriction, constraint, or limit on another entity or its behavior.
-
B.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
C.
definesLimitOf
chosen
Indicates that one entity specifies or establishes the maximum or boundary condition applicable to another entity.
-
D.
limitBehavior
Indicates how an entity behaves or changes as it approaches a specified limit or boundary condition.
-
E.
gLimit
Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2c44288190a105761ae646989e |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.