Triple
T37174222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSC |
E920995
|
entity |
| Predicate | commonlyUsesDyeType |
P199430
|
FINISHED |
| Object | ruthenium-based dye |
—
|
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: ruthenium-based dye | Statement: [DSC, commonlyUsesDyeType, ruthenium-based dye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyUsesDyeType Context triple: [DSC, commonlyUsesDyeType, ruthenium-based dye]
-
A.
usesDyes
Indicates that one entity employs or applies dyes in relation to another entity or process.
-
B.
dyeColor
Indicates that one entity has a specific color resulting from a dye applied to it.
-
C.
canBeDyed
Indicates that an entity has the property of being able to undergo a dyeing process to change or add color.
-
D.
dyeComponent
Indicates that one entity is a constituent or ingredient used to produce or formulate a dye in relation to another entity.
-
E.
colorUse
Indicates that one entity uses, applies, or is associated with a particular color in its appearance, design, or representation.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
| PDg | Predicate description generation | batch_69ff38b8843c819097359a4d77e9d442 |
completed | May 9, 2026, 1:38 p.m. |
Created at: May 3, 2026, 4:15 p.m.