Triple
T14631785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N75 |
E343494
|
entity |
| Predicate | hasExternalDisplayResolution |
P83513
|
FINISHED |
| Object | 160 x 128 pixels |
—
|
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: 160 x 128 pixels | Statement: [Nokia N75, hasExternalDisplayResolution, 160 x 128 pixels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExternalDisplayResolution Context triple: [Nokia N75, hasExternalDisplayResolution, 160 x 128 pixels]
-
A.
externalDisplayResolution
chosen
Indicates the resolution at which content is output or rendered on an external display device.
-
B.
supportsExternalDisplay
Indicates that an entity is capable of connecting to and functioning with an external display device.
-
C.
maximumExternalDisplays
Indicates the highest number of external display devices that can be simultaneously connected to and used with a given system or component.
-
D.
supportsDisplayResolution
Indicates that one entity is capable of operating with, rendering, or otherwise accommodating the specified display resolution of another entity.
-
E.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4a912248190a3df7f821395c776 |
completed | April 14, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.