Triple
T12345743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia C6-01 |
E294348
|
entity |
| Predicate | supportsHSDPA |
P102678
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nokia C6-01, supportsHSDPA, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHSDPA Context triple: [Nokia C6-01, supportsHSDPA, yes]
-
A.
supports3G
chosen
Indicates that one entity provides or is compatible with 3G mobile network connectivity for another entity or for its operation.
-
B.
supportsLTE
Indicates that one entity provides compatibility with or functionality for LTE (Long-Term Evolution) cellular communication for another entity.
-
C.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
D.
supportsTethering
Indicates that one entity enables or allows another entity to share its network connection with additional devices (i.e., provides tethering capability).
-
E.
hasCellularComponent
Indicates that an entity possesses, includes, or is associated with a specific cellular component as part of its structure or organization.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7a4a448190aa70d66dc2f406c1 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.