Triple
T35826103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chronochrome color system |
E1035646
|
entity |
| Predicate | colorMethod |
P185362
|
FINISHED |
| Object | additive |
—
|
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: additive | Statement: [Chronochrome color system, colorMethod, additive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorMethod Context triple: [Chronochrome color system, colorMethod, additive]
-
A.
colorUse
Indicates that one entity uses, applies, or is associated with a particular color in its appearance, design, or representation.
-
B.
colorationFunction
Indicates a relationship where an entity’s coloration serves a particular role or purpose, such as camouflage, signaling, or protection.
-
C.
colorSelection
Indicates the relationship in which an entity chooses or is assigned a specific color from a set of possible colors.
-
D.
colorBehavior
Indicates how an entity’s color changes, appears, or is used under certain conditions or interactions.
-
E.
colorComponent
Indicates that one entity is a component or constituent part of the overall color of another entity.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: May 3, 2026, 4:06 p.m.