Triple
T38023791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 6680 |
E948712
|
entity |
| Predicate | UMTSBand |
P171922
|
FINISHED |
| Object | 2100 |
—
|
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: 2100 | Statement: [Nokia 6680, UMTSBand, 2100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UMTSBand Context triple: [Nokia 6680, UMTSBand, 2100]
-
A.
frequencyBandSupported
Indicates that an entity supports operation or functionality within a specified frequency band.
-
B.
carrierFrequency
Indicates the frequency at which a carrier signal or carrier wave operates in a communication or modulation process.
-
C.
telecommunicationsBand
chosen
Indicates a relationship where a specific telecommunications frequency band is used, allocated, or associated with a communication system, service, or technology.
-
D.
spectralBandUse
Indicates how specific spectral bands are utilized or applied within a given context or process.
-
E.
transmissionBand
Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.