Triple
T11559775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dramatically Different Moisturizing Lotion |
E274110
|
entity |
| Predicate | useAfter |
P5014
|
FINISHED |
| Object | cleansing |
—
|
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: cleansing | Statement: [Dramatically Different Moisturizing Lotion, useAfter, cleansing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useAfter Context triple: [Dramatically Different Moisturizing Lotion, useAfter, cleansing]
-
A.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
-
B.
after
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
C.
useAfterRenovation
Indicates that something is intended to be used or occupied only after renovation work has been completed.
-
D.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
E.
subsequentUse
chosen
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88a899d4481909a3bce3147763b51 |
completed | April 10, 2026, 5:28 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.