Triple
T19600652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breck Coleman |
E470463
|
entity |
| Predicate | workColorProcess |
P21943
|
FINISHED |
| Object | black-and-white |
—
|
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: black-and-white | Statement: [Breck Coleman, workColorProcess, black-and-white]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workColorProcess Context triple: [Breck Coleman, workColorProcess, black-and-white]
-
A.
color work
Indicates that an entity applies or adds color to another entity, typically as part of a creative or finishing process.
-
B.
hasColorProcess
chosen
Indicates a relationship where an entity is associated with a specific method or process used to apply, change, or manage its color.
-
C.
colorTreatment
Indicates that an entity has undergone a process or action that changes, enhances, or assigns its color.
-
D.
colors
Indicates that one entity assigns, describes, or provides the color or colors of another entity.
-
E.
handleColor
Indicates that an entity has a handle whose color is specified or characterized by the related value or 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6407df98c8190b258ac3b690fe4b1 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.