Triple
T36454130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Instruments Calypso-based phones |
E898102
|
entity |
| Predicate | radioTechnology |
P109039
|
FINISHED |
| Object | GSM 900 |
—
|
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 900 | Statement: [Texas Instruments Calypso-based phones, radioTechnology, GSM 900]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioTechnology Context triple: [Texas Instruments Calypso-based phones, radioTechnology, GSM 900]
-
A.
radioInterface
Indicates a relationship where one entity provides or defines the radio communication interface used by another entity for wireless connectivity or control.
-
B.
radioSystem
chosen
Indicates that one entity functions as, or is equipped with, a radio communication system used for transmitting and/or receiving signals.
-
C.
radioStructure
Indicates a structural or organizational relationship involving radio components, systems, or configurations.
-
D.
radioVersionType
Indicates the specific type or category of a radio version associated with an item or entity.
-
E.
radioVersionName
Indicates the specific name or label assigned to a version of a radio-related item or system.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.