Triple
T9387696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S1850M long-range radar |
E225944
|
entity |
| Predicate | maxInstrumentedRange |
P22930
|
FINISHED |
| Object | 400 km |
—
|
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: 400 km | Statement: [S1850M long-range radar, maxInstrumentedRange, 400 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxInstrumentedRange Context triple: [S1850M long-range radar, maxInstrumentedRange, 400 km]
-
A.
maximumExtent
chosen
Indicates the greatest or furthest degree, size, or range to which something can extend or apply within a given context.
-
B.
isHighestRangeOf
Indicates that one entity represents the maximum or topmost range or interval within which another entity falls or is categorized.
-
C.
minimumRange
Indicates the smallest allowable or observed value within a specified range for a given relationship or measurement.
-
D.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
E.
majorRangeIncludes
Indicates that a major range (such as a primary geographic or categorical span) encompasses or contains another specified range.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d562a48190875d9fe3aae25a2b |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.