Triple
T26474774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VERA |
E665996
|
entity |
| Predicate | observesFrequencyBand |
P38137
|
FINISHED |
| Object | 22 GHz |
—
|
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: 22 GHz | Statement: [VERA, observesFrequencyBand, 22 GHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observesFrequencyBand Context triple: [VERA, observesFrequencyBand, 22 GHz]
-
A.
observingBand
chosen
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
-
B.
frequencyBandSupported
Indicates that an entity supports operation or functionality within a specified frequency band.
-
C.
observesBand
Indicates that one entity watches, studies, or monitors a musical band.
-
D.
canObserveFrequency
Indicates that one entity has the capability to detect, measure, or monitor the frequency of another entity or signal.
-
E.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 12:22 a.m.