Triple
T11559764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dramatically Different Moisturizing Lotion |
E274110
|
entity |
| Predicate | stepInRoutine |
P100318
|
FINISHED |
| Object | Step 3 |
—
|
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: Step 3 | Statement: [Dramatically Different Moisturizing Lotion, stepInRoutine, Step 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stepInRoutine Context triple: [Dramatically Different Moisturizing Lotion, stepInRoutine, Step 3]
-
A.
stepTakes
Indicates that one step directly follows or is taken after another step in a process or sequence.
-
B.
stepReturns
Indicates that a particular step in a process or workflow yields, outputs, or hands back a specified result or value.
-
C.
stepRelative
Indicates a familial relationship where one person is a step-relative of another, such as a step-parent, step-child, or step-sibling, created through marriage rather than blood or adoption.
-
D.
stepCount
Indicates the number of discrete steps taken or required in a process, sequence, or movement.
-
E.
firstStepIn
Indicates that one event, action, or process is the initial step in a larger sequence or procedure involving another.
- 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_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. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:37 p.m.