Triple
T12556718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3100 |
E295235
|
entity |
| Predicate | gprsClass |
P56285
|
FINISHED |
| Object | Class 6 |
—
|
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: Class 6 | Statement: [Nokia 3100, gprsClass, Class 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gprsClass Context triple: [Nokia 3100, gprsClass, Class 6]
-
A.
serviceNumberOrClass
Indicates that one entity specifies the service identifier or class designation associated with another entity.
-
B.
hasCommunicationClass
chosen
Indicates that one entity is assigned to, or associated with, a particular category or class of communication.
-
C.
signalingMode
Indicates the method or mechanism by which one entity communicates or transmits signals to another.
-
D.
bandwidthClass
Indicates the classification of a connection or resource based on its available or allocated bandwidth capacity.
-
E.
roleIn3GPP
Indicates that an entity holds a specific role or function within the context of 3GPP (Third Generation Partnership Project) standards or activities.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 11:47 p.m.