Triple
T1936399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liquid Retina XDR |
E41452
|
entity |
| Predicate | usesBacklightTechnology |
P33708
|
FINISHED |
| Object | mini-LED |
—
|
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: mini-LED | Statement: [Liquid Retina XDR, usesBacklightTechnology, mini-LED]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBacklightTechnology Context triple: [Liquid Retina XDR, usesBacklightTechnology, mini-LED]
-
A.
hasBacklitKeyboard
Indicates that an entity is equipped with a keyboard that includes built-in lighting behind the keys.
-
B.
supportsWideColorGamut
Indicates that one entity provides or enables compatibility with a wide color gamut capability for another entity or context.
-
C.
lightingCharacteristic
Indicates the specific qualities or properties of how something is lit, such as brightness, color, direction, or style of illumination.
-
D.
hasAlwaysOnDisplay
Indicates that an entity features an always-on display capability that remains visible without fully waking the device.
-
E.
led
Indicates that one entity guided, directed, or was in charge of another entity or activity, typically over a period of time.
- F. None of above. chosen
Provenance (4 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2c5f6e481909b2d95861e2098f9 |
completed | March 7, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb25ef0ec8190b907963e9db0fe04 |
completed | March 7, 2026, 5:06 a.m. |
Created at: March 4, 2026, 7:35 p.m.