Triple
T17982986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 6101 |
E430150
|
entity |
| Predicate | mobileNetworkStandard |
P125698
|
FINISHED |
| Object | GSM |
—
|
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 | Statement: [Nokia 6101, mobileNetworkStandard, GSM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobileNetworkStandard Context triple: [Nokia 6101, mobileNetworkStandard, GSM]
-
A.
publicTelecomOperator
Indicates that an entity functions as a telecommunications service provider that is publicly owned, controlled, or designated to operate in the public interest.
-
B.
cellularOptions
Indicates that one entity specifies or provides available cellular network or mobile connectivity options for another entity.
-
C.
wirelessOperator
Indicates that an entity operates, manages, or provides services for a wireless communication system or network for another entity.
-
D.
telecommunicationsProvider
Indicates that one entity provides telecommunications services (such as phone, internet, or data connectivity) to another entity.
-
E.
telecommunicationsType
chosen
Indicates the specific category or mode of telecommunications service or technology associated with 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b297b7108190a676409b330ca23b |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.