Triple
T10550664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class G airspace |
E248937
|
entity |
| Predicate | surveillanceCoverage |
P85626
|
FINISHED |
| Object | may be limited or absent |
—
|
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: may be limited or absent | Statement: [Class G airspace, surveillanceCoverage, may be limited or absent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveillanceCoverage Context triple: [Class G airspace, surveillanceCoverage, may be limited or absent]
-
A.
sensorCoverage
chosen
Indicates that a sensor’s detection or monitoring area spatially covers or includes a given region, object, or point.
-
B.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
C.
digitalCoverage
Indicates that one entity provides or has access to digital services, connectivity, or online resources for another entity or within a specified area.
-
D.
surveyCoverage
Indicates that one entity’s survey or data collection activity extends over, includes, or accounts for another entity or area.
-
E.
hasFrequencyCoverage
Indicates that one entity provides, supports, or is applicable across a specified range or set of frequencies associated with 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52710869c81909b6db1a190825bad |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:34 p.m.