Triple
T21481894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ansco Color |
E530012
|
entity |
| Predicate | processing |
P35348
|
FINISHED |
| Object | proprietary Ansco color chemistry |
—
|
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: proprietary Ansco color chemistry | Statement: [Ansco Color, processing, proprietary Ansco color chemistry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processing Context triple: [Ansco Color, processing, proprietary Ansco color chemistry]
-
A.
processingUse
chosen
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
B.
processedTo
Indicates that one entity is transformed or converted into another entity through some processing operation.
-
C.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
-
D.
processingOrder
Indicates the sequence or priority in which items, tasks, or requests are to be processed or handled.
-
E.
pipeline
Indicates a sequential process or workflow where the output of one stage is passed as input to the next to achieve a final result.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea338f988190a3044f8d02a567fe |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:21 p.m.