Triple
T9801456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | That Yellow Bastard |
E237845
|
entity |
| Predicate | pageColoring |
P87298
|
FINISHED |
| Object | primarily black-and-white with spot color |
—
|
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: primarily black-and-white with spot color | Statement: [That Yellow Bastard, pageColoring, primarily black-and-white with spot color]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pageColoring Context triple: [That Yellow Bastard, pageColoring, primarily black-and-white with spot color]
-
A.
printingColor
Indicates that one entity uses or displays a specific color in the context of printing or printed output.
-
B.
printedInColor
chosen
Indicates that something was produced or reproduced using multiple ink colors rather than only black-and-white.
-
C.
parchmentColor
Indicates that one entity has the color characteristic of parchment in relation to another entity.
-
D.
colorImaging
Indicates a relationship where an entity captures, processes, or represents visual information specifically in terms of color.
-
E.
color work
Indicates that an entity applies or adds color to another entity, typically as part of a creative or finishing process.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda62a11a88190880e0cce24923b14 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.