Triple
T37546017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Even Better moisturizer |
E933464
|
entity |
| Predicate | partOfRegimen |
P37862
|
FINISHED |
| Object | Clinique Even Better routine |
—
|
NE NERFINISHED |
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: Clinique Even Better routine | Statement: [Even Better moisturizer, partOfRegimen, Clinique Even Better routine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfRegimen Context triple: [Even Better moisturizer, partOfRegimen, Clinique Even Better routine]
-
A.
controlRegimen
Indicates that an entity is responsible for directing, managing, or governing a particular regimen, protocol, or set of prescribed procedures.
-
B.
belongsToRegimen
chosen
Indicates that something is a component or member of a specified regimen or structured treatment plan.
-
C.
partOfPlan
Indicates that one entity is included as a component or step within a broader plan or strategy.
-
D.
regimenDependsOn
Indicates that the applicability or outcome of a regimen is contingent upon another specified factor, condition, or regimen.
-
E.
regimenCharacteristic
Indicates that a specified property or feature characterizes a particular regimen (such as a treatment, protocol, or routine).
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a017bc21b048190b9c680013de203b6 |
completed | May 11, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_6a017aa09c4481909c3b55e0cd13501e |
completed | May 11, 2026, 6:43 a.m. |
Created at: May 3, 2026, 4:17 p.m.