Triple
T32361356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topol |
E826869
|
entity |
| Predicate | operationalRangeCategory |
P133442
|
FINISHED |
| Object | ICBM-class |
—
|
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: ICBM-class | Statement: [Topol, operationalRangeCategory, ICBM-class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalRangeCategory Context triple: [Topol, operationalRangeCategory, ICBM-class]
-
A.
operationalRange
Indicates the span of conditions (such as distance, time, or environment) within which a system, device, or process can function effectively and safely.
-
B.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
C.
hasRangeCategory
chosen
Indicates that a property or measurement falls within a specified category or interval of possible values.
-
D.
operatingTemperatureCategory
Indicates the temperature range classification within which an entity is designed or expected to operate.
-
E.
operationalCeilingClass
Indicates the classification of an entity based on the maximum altitude or height at which it is designed or permitted to operate.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
Created at: May 1, 2026, 12:49 a.m.