Triple
T7646441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rouge Volupté Shine |
E173135
|
entity |
| Predicate | finishDescription |
P77795
|
FINISHED |
| Object | glossy, wet-look shine |
—
|
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: glossy, wet-look shine | Statement: [Rouge Volupté Shine, finishDescription, glossy, wet-look shine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finishDescription Context triple: [Rouge Volupté Shine, finishDescription, glossy, wet-look shine]
-
A.
finish
Indicates that an entity brings an action, process, or state to an end or completion.
-
B.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
C.
finishOptions
Indicates that one entity specifies or controls the possible ways in which another entity can be completed, finalized, or brought to an end.
-
D.
finished
Indicates that an entity has completed an action, process, or state, reaching its end point.
-
E.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faf3bd388190a8cb0f13322a7c00 |
completed | March 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e9ef1c81909c8bff716541ac1f |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8195e5c8190835e28d44e19f6ef |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:58 p.m.