Triple
T10909986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VOR/DME |
E257669
|
entity |
| Predicate | frequencyAllocation |
P68289
|
FINISHED |
| Object | VOR frequency band |
—
|
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: VOR frequency band | Statement: [VOR/DME, frequencyAllocation, VOR frequency band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyAllocation Context triple: [VOR/DME, frequencyAllocation, VOR frequency band]
-
A.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
B.
frequencyRegion
Indicates that something is associated with, occurs within, or is characterized by a particular range or band of frequencies.
-
C.
frequencyBandSupported
chosen
Indicates that an entity supports operation or functionality within a specified frequency band.
-
D.
frequencyCategory
Indicates how often an action, event, or relationship occurs, typically by assigning it to a qualitative frequency level (e.g., rare, occasional, frequent).
-
E.
numberOfFrequencyBands
Indicates the relationship specifying how many distinct frequency bands are associated with or used by an 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77068e5488190bbc881ebf51d6b2e |
completed | April 9, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.