Triple
T33203315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DisplayHDR |
E849961
|
entity |
| Predicate | featureTested |
P40583
|
FINISHED |
| Object | peak luminance |
—
|
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: peak luminance | Statement: [DisplayHDR, featureTested, peak luminance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featureTested Context triple: [DisplayHDR, featureTested, peak luminance]
-
A.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
C.
documentedFeature
Indicates that a feature has been formally recorded or described in documentation.
-
D.
testedFor
chosen
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
E.
testedUnder
Indicates that one entity is examined, evaluated, or experimented on while being subject to the conditions, environment, or parameters specified by another entity.
- 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_6a017969ff908190a7a1a46b3f5ae362 |
completed | May 11, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a017609ff4c8190aba8a1864d39a608 |
completed | May 11, 2026, 6:24 a.m. |
Created at: May 1, 2026, 1:30 a.m.