Triple
T32988185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 5154 Enhanced Color Display |
E844004
|
entity |
| Predicate | colorPhosphorType |
P174391
|
FINISHED |
| Object | RGB phosphor |
—
|
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: RGB phosphor | Statement: [IBM 5154 Enhanced Color Display, colorPhosphorType, RGB phosphor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorPhosphorType Context triple: [IBM 5154 Enhanced Color Display, colorPhosphorType, RGB phosphor]
-
A.
colorDisplay
Indicates that one entity presents, shows, or renders the color associated with another entity.
-
B.
colorModeType
chosen
Indicates the type or scheme of color representation or processing applied to an entity (e.g., grayscale, RGB, CMYK).
-
C.
colorUse
Indicates that one entity uses, applies, or is associated with a particular color in its appearance, design, or representation.
-
D.
colorSystem
Indicates that one entity is a system or scheme used to define, organize, or represent the colors of another entity.
-
E.
colorComponent
Indicates that one entity is a component or constituent part of the overall color of 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: May 1, 2026, 1:22 a.m.