Triple
T24811988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-15 early warning radar |
E620814
|
entity |
| Predicate | typicalAltitudeCoverage |
P17150
|
FINISHED |
| Object | low altitude |
—
|
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: low altitude | Statement: [P-15 early warning radar, typicalAltitudeCoverage, low altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAltitudeCoverage Context triple: [P-15 early warning radar, typicalAltitudeCoverage, low altitude]
-
A.
altitudeCoverageCharacteristic
chosen
Indicates the range or specific values of altitude over which something (such as a system, sensor, or service) is designed to operate or provide coverage.
-
B.
elevationCoverageApproximate
Indicates an approximate or estimated representation of how elevation values are covered or distributed over a given area or dataset.
-
C.
typicalElevationRange
Indicates the usual range of elevation values within which something commonly occurs or exists.
-
D.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
E.
typicalCamp1Altitude_m
Indicates the usual or characteristic altitude, in meters, at which the first camp in a sequence of camps is located.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 18, 2026, 4:50 a.m.