Triple
T12594393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GBTT |
E300696
|
entity |
| Predicate | radioBand |
P1685
|
FINISHED |
| Object | medium frequency |
—
|
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: medium frequency | Statement: [GBTT, radioBand, medium frequency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioBand Context triple: [GBTT, radioBand, medium frequency]
-
A.
frequencyBand
chosen
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
B.
radioInterface
Indicates a relationship where one entity provides or defines the radio communication interface used by another entity for wireless connectivity or control.
-
C.
radioRestrictions
Indicates that there are specific limitations or rules governing the use or operation of radio communications between the related entities.
-
D.
frequencyBandSupported
Indicates that an entity supports operation or functionality within a specified frequency band.
-
E.
broadcastBand
Indicates that something is transmitted over a particular broadcast frequency band (e.g., AM, FM, VHF, UHF) for distribution to receivers.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:08 p.m.