Triple
T33203328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DisplayHDR |
E849961
|
entity |
| Predicate | tieringBasis |
P7476
|
FINISHED |
| Object | minimum peak luminance levels |
—
|
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: minimum peak luminance levels | Statement: [DisplayHDR, tieringBasis, minimum peak luminance levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieringBasis Context triple: [DisplayHDR, tieringBasis, minimum peak luminance levels]
-
A.
tierDeterminedBy
Indicates that the classification level or rank of one entity is decided or derived based on the properties, status, or outcome associated with another entity.
-
B.
tiered
Indicates that something is organized into multiple hierarchical levels or layers, often with differing degrees of priority, access, or benefit.
-
C.
tierType
Indicates the classification level or rank assigned to an entity within a multi-level or hierarchical system.
-
D.
rankingBasis
chosen
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
E.
hasTierStructure
Indicates that something is organized into distinct hierarchical levels or layers within a structured system.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.