Triple
T31386189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hahn/Cock |
E800600
|
entity |
| Predicate | usesColorAsConcept |
P46606
|
FINISHED |
| Object | International Klein Blue–like monochrome |
—
|
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: International Klein Blue–like monochrome | Statement: [Hahn/Cock, usesColorAsConcept, International Klein Blue–like monochrome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesColorAsConcept Context triple: [Hahn/Cock, usesColorAsConcept, International Klein Blue–like monochrome]
-
A.
colorUse
Indicates that one entity uses, applies, or is associated with a particular color in its appearance, design, or representation.
-
B.
isColor
Indicates that one entity represents the color attribute or hue of another entity.
-
C.
colorHasMeaning
chosen
Indicates that a particular color is associated with or conveys a specific meaning, symbolism, or significance.
-
D.
containsColor
Indicates that one entity includes or exhibits the color specified by another entity.
-
E.
colors
Indicates that one entity assigns, describes, or provides the color or colors 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 29, 2026, 9:19 p.m.