Triple
T38149058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia Series 90 |
E952700
|
entity |
| Predicate | commercialDevice |
P191745
|
FINISHED |
| Object | Nokia 7710 |
—
|
NE NERFINISHED |
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: Nokia 7710 | Statement: [Nokia Series 90, commercialDevice, Nokia 7710]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialDevice Context triple: [Nokia Series 90, commercialDevice, Nokia 7710]
-
A.
commercialProduct
Indicates that one entity is a product or service offered for sale or commercial use by another entity.
-
B.
usedAsDeviceFor
Indicates that one entity functions as a tool, instrument, or device for performing an action or achieving a particular purpose for another entity.
-
C.
commercialDeployment
Indicates that something has been put into active use or operation in a real-world commercial context, typically as a product or service offered to customers.
-
D.
commercialArm
Indicates that an entity functions as the business or revenue-generating division/branch of another organization.
-
E.
device
Indicates that one entity is a device used, controlled, or referenced by another entity in the relationship.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:21 p.m.