Triple
T7177985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interim Agreement on Offensive Arms |
E167367
|
entity |
| Predicate | setsCeilingFor |
P75040
|
FINISHED |
| Object | number of ICBM launchers for each side |
—
|
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: number of ICBM launchers for each side | Statement: [Interim Agreement on Offensive Arms, setsCeilingFor, number of ICBM launchers for each side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsCeilingFor Context triple: [Interim Agreement on Offensive Arms, setsCeilingFor, number of ICBM launchers for each side]
-
A.
ceiling
Indicates that one entity is the smallest value that is greater than or equal to another value, typically representing a rounding-up operation.
-
B.
maximumCeiling
chosen
Indicates the highest allowable or achievable limit or value that something cannot exceed.
-
C.
ceilingHeight
Indicates the vertical distance from the floor to the ceiling in a given space.
-
D.
hasCeilingType
Indicates that an entity is associated with or characterized by a specific type of ceiling.
-
E.
hasCeiling
Indicates that one entity possesses or is characterized by an upper limit, boundary, or maximum value defined by another entity.
- 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_69c68889a2748190a316c5e65360361a |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e74fb0f48190b2ad4dd4efdd241a |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:49 p.m.