Triple
T14631784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia N75 |
E343494
|
entity |
| Predicate | hasExternalDisplaySize |
P83512
|
FINISHED |
| Object | 1.36 inches |
—
|
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: 1.36 inches | Statement: [Nokia N75, hasExternalDisplaySize, 1.36 inches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExternalDisplaySize Context triple: [Nokia N75, hasExternalDisplaySize, 1.36 inches]
-
A.
externalDisplaySize
chosen
Indicates the size or dimensions of an external display associated with an entity.
-
B.
supportsExternalDisplay
Indicates that an entity is capable of connecting to and functioning with an external display device.
-
C.
externalDisplayResolution
Indicates the resolution at which content is output or rendered on an external display device.
-
D.
integratedDisplaySize
Indicates the size or dimensions of a built-in or non-detachable display associated with an entity.
-
E.
maximumExternalDisplays
Indicates the highest number of external display devices that can be simultaneously connected to and used with a given system or component.
- 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.