Triple
T21192170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPRS |
E522238
|
entity |
| Predicate | usesRadioInterface |
P23646
|
FINISHED |
| Object | GSM TDMA channels |
—
|
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: GSM TDMA channels | Statement: [GPRS, usesRadioInterface, GSM TDMA channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRadioInterface Context triple: [GPRS, usesRadioInterface, GSM TDMA channels]
-
A.
hasRadio
Indicates that an entity is equipped with or includes a radio device.
-
B.
containsRadioSource
Indicates that one entity includes or encompasses a radio source within its spatial or structural extent.
-
C.
hasRadioStation
Indicates that one entity possesses, operates, or is served by a particular radio station.
-
D.
radioInterface
chosen
Indicates a relationship where one entity provides or defines the radio communication interface used by another entity for wireless connectivity or control.
-
E.
isRadioFriendly
Indicates that something (typically a song, track, or audio content) is suitable for broadcast on mainstream radio, usually by meeting content, length, and formatting standards.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733381f288190b3da795f62a39568 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.