Triple
T21809753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Génifique Youth Activating Serum |
E538439
|
entity |
| Predicate | recommendedUsageFrequency |
P145737
|
FINISHED |
| Object | twice daily |
—
|
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: twice daily | Statement: [Advanced Génifique Youth Activating Serum, recommendedUsageFrequency, twice daily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedUsageFrequency Context triple: [Advanced Génifique Youth Activating Serum, recommendedUsageFrequency, twice daily]
-
A.
serviceFrequencyType
Indicates how often a service occurs or is scheduled within a given time period.
-
B.
serviceFrequencyContext
Indicates the contextual conditions or circumstances under which a service’s frequency is defined, applied, or interpreted.
-
C.
appointmentFrequency
Indicates how often appointments are scheduled or expected to occur within a given time period.
-
D.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
E.
frequentUseCase
Indicates a situation, scenario, or pattern of use that occurs regularly or more often than others in relation to the subject.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc4809c8190853e2777a1f573d4 |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c670ee608190b9cfdc09de74f0de |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 6:53 p.m.