Triple
T15410883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N8 |
E368585
|
entity |
| Predicate | hasPhysicalKeys |
P85055
|
FINISHED |
| Object | volume rocker |
—
|
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: volume rocker | Statement: [Nokia N8, hasPhysicalKeys, volume rocker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhysicalKeys Context triple: [Nokia N8, hasPhysicalKeys, volume rocker]
-
A.
hasPhysicalKeypad
Indicates that an entity is equipped with a tangible, button-based keypad for input or control.
-
B.
hasPhysicalControl
Indicates that one entity currently exercises direct, tangible control or possession over another entity or object.
-
C.
hasFunctionKeys
chosen
Indicates that an object or device possesses dedicated keys assigned to specific functions or shortcuts.
-
D.
hasPhysicalCard
Indicates that an entity possesses or is associated with a tangible, real-world card object.
-
E.
hasPhysicalInterface
Indicates that one entity provides or includes a tangible, hardware-based connection point or medium through which another entity can physically interact or communicate.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea600b48190a3dbca1a68a2a1cd |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.