Triple
T12718056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3350 |
E303899
|
entity |
| Predicate | networkBand |
P106325
|
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: [Nokia 3350, networkBand, GSM 900]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkBand Context triple: [Nokia 3350, networkBand, GSM 900]
-
A.
network
Indicates that one entity is connected to or interacts with another through a system of relationships, communication, or information exchange.
-
B.
networkServed
Indicates that a network provides connectivity or services to a particular entity or set of entities.
-
C.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
D.
inNetwork
Indicates that one entity is within the same defined network, system, or coverage group as another entity, such that network-based interactions or benefits apply between them.
-
E.
networkArea
Indicates that one entity defines, covers, or is responsible for a specific network area associated with another entity.
- F. None of above. chosen
Provenance (4 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9625d9da48190ab377f9328a0e1f5 |
completed | April 10, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:23 p.m.