Triple
T16853000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samsung Display |
E409719
|
entity |
| Predicate | colorConversionMaterial |
P81654
|
FINISHED |
| Object | quantum dots |
—
|
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: quantum dots | Statement: [Samsung Display, colorConversionMaterial, quantum dots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorConversionMaterial Context triple: [Samsung Display, colorConversionMaterial, quantum dots]
-
A.
materialCompatibility
chosen
Indicates that two or more materials are suitable to be used together without causing adverse interactions, degradation, or performance issues.
-
B.
shadeMaterial
Indicates that one entity serves as the material or substance used to provide shade for another entity.
-
C.
colorImaging
Indicates a relationship where an entity captures, processes, or represents visual information specifically in terms of color.
-
D.
colorSystem
Indicates that one entity is a system or scheme used to define, organize, or represent the colors of another entity.
-
E.
coversColorSpace
Indicates that one entity’s color representation range fully includes or spans the color space defined 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37abadc81909d02d329403497d6 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.