Triple
T38093034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justine |
E951163
|
entity |
| Predicate | workColorFormat |
P190011
|
FINISHED |
| Object | black-and-white film |
—
|
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 film | Statement: [Justine, workColorFormat, black-and-white film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workColorFormat Context triple: [Justine, workColorFormat, black-and-white film]
-
A.
color work
Indicates that an entity applies or adds color to another entity, typically as part of a creative or finishing process.
-
B.
writingSupportColor
Indicates the color of the surface or medium that supports the writing (e.g., the background or material on which text is written).
-
C.
basedInWorkFormat
Indicates that an entity operates or is situated within a particular work format (such as remote, hybrid, or on-site) as its primary mode of working.
-
D.
colorUse
Indicates that one entity uses, applies, or is associated with a particular color in its appearance, design, or representation.
-
E.
wordFormat
Indicates that one entity specifies the written or typographical form in which another entity (typically a word or text) is presented.
- F. None of above. chosen
Provenance (4 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_69f76f04960c8190a83f14ae4c67f5bc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fc4747b06c8190a3ea5331f02eedad |
completed | May 7, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:21 p.m.