Triple
T15174125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N95 |
E362560
|
entity |
| Predicate | hasDedicatedMediaKeys |
P116999
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nokia N95, hasDedicatedMediaKeys, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDedicatedMediaKeys Context triple: [Nokia N95, hasDedicatedMediaKeys, true]
-
A.
keySystem
Indicates a relationship where one entity functions as the primary or controlling system that governs, secures, or coordinates access to another entity or set of entities.
-
B.
supportsPhysicalMedia
Indicates that one entity provides the capability to use, read, or handle physical media formats (such as discs, tapes, or printed materials) associated with another entity.
-
C.
supportsMediaManagement
Indicates that one entity provides functionality or assistance for organizing, handling, or controlling media content for another entity.
-
D.
supportsVideoPlayback
Indicates that an entity is capable of playing or rendering video content.
-
E.
usesDRM
Indicates that one entity applies digital rights management (DRM) controls or technologies to another entity (such as content, software, or media).
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006501b488190a2ab09dbf1532571 |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb9779acc81908ed2dad382c42dca |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:09 a.m.