Triple
T37946031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 9500 Communicator |
E946607
|
entity |
| Predicate | internalDisplayType |
P5731
|
FINISHED |
| Object | color LCD |
—
|
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: color LCD | Statement: [Nokia 9500 Communicator, internalDisplayType, color LCD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalDisplayType Context triple: [Nokia 9500 Communicator, internalDisplayType, color LCD]
-
A.
hasInternalDisplay
Indicates that an entity is equipped with a built-in display screen as part of its own hardware.
-
B.
displayType
Indicates the manner or format in which something is presented, shown, or rendered.
-
C.
integratedDisplay
Indicates that a display is built into and forms a unified part of another device or system, rather than being a separate external unit.
-
D.
hasDisplayType
chosen
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
E.
dataTypeDisplayed
Indicates that a particular data type is currently being shown or rendered in a given context or interface.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 3, 2026, 4:20 p.m.