Triple
T2796399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro Display XDR |
E53046
|
entity |
| Predicate | backlightSystem |
P33708
|
FINISHED |
| Object | full‑array local dimming |
—
|
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: full‑array local dimming | Statement: [Pro Display XDR, backlightSystem, full‑array local dimming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backlightSystem Context triple: [Pro Display XDR, backlightSystem, full‑array local dimming]
-
A.
usesBacklightTechnology
chosen
Indicates that one entity employs backlight technology to illuminate or enhance the visibility of another entity or its display.
-
B.
hasBacklitKeyboard
Indicates that an entity is equipped with a keyboard that includes built-in lighting behind the keys.
-
C.
lightingControlledBy
Indicates that the lighting system or device is operated, regulated, or influenced by a specified controller or control mechanism.
-
D.
systemBoard
Indicates a relationship where a system is associated with, mounted on, or implemented via a particular main circuit board (motherboard) that hosts its core components.
-
E.
maximumBrightness
Indicates the highest level of brightness that an entity can reach or exhibit.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abddef754081908e6218dc2208e0fd |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.