Triple
T10401871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebamed Baby |
E245167
|
entity |
| Predicate | hasIntendedFunction |
P13995
|
FINISHED |
| Object | protect baby skin barrier |
—
|
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: protect baby skin barrier | Statement: [Sebamed Baby, hasIntendedFunction, protect baby skin barrier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntendedFunction Context triple: [Sebamed Baby, hasIntendedFunction, protect baby skin barrier]
-
A.
intendedFunction
chosen
Indicates that something is designed or purposed to perform a particular role, use, or function.
-
B.
hasIntendedEffect
Indicates that one entity is expected or designed to produce a particular effect or outcome on another entity or context.
-
C.
hasIntent
Indicates that an entity possesses a purpose, plan, or goal directing its actions or behavior toward a particular outcome.
-
D.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
E.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9e42da08190a5383df3df6d3c18 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:08 p.m.