Triple
T14453924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dynamic AMOLED display |
E358404
|
entity |
| Predicate | blueLightReductionPurpose |
P21011
|
FINISHED |
| Object | reduced eye strain |
—
|
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: reduced eye strain | Statement: [Dynamic AMOLED display, blueLightReductionPurpose, reduced eye strain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blueLightReductionPurpose Context triple: [Dynamic AMOLED display, blueLightReductionPurpose, reduced eye strain]
-
A.
reasonForBrightness
Indicates the cause or explanation for why something is bright or has a certain level of brightness.
-
B.
screenProtection
Indicates that one entity provides or has a protective layer or feature designed to safeguard a screen from damage or wear.
-
C.
reasonForUse
chosen
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
D.
blueShade
Indicates that one entity has a color that is a specific shade or variation of blue.
-
E.
usesBacklightTechnology
Indicates that one entity employs backlight technology to illuminate or enhance the visibility of another entity or its 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91a8bf088190abf5fd4f646b8c62 |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.