Triple
T27660266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juvederm |
E697101
|
entity |
| Predicate | containsOptionalComponent |
P31918
|
FINISHED |
| Object | lidocaine |
—
|
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: lidocaine | Statement: [Juvederm, containsOptionalComponent, lidocaine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsOptionalComponent Context triple: [Juvederm, containsOptionalComponent, lidocaine]
-
A.
hasSubcomponent
Indicates that one entity is a constituent part or component of another, larger entity.
-
B.
componentIncluded
Indicates that one entity is a constituent part or subcomponent that is contained within or included in another entity.
-
C.
mayRequireComponent
chosen
Indicates that one entity can optionally depend on or need another entity as a component for its proper use or operation.
-
D.
hasComponentForm
Indicates that one entity exists as a structural or compositional form or variant of another entity.
-
E.
isComponentAlongWith
Indicates that an entity functions as a component in conjunction with one or more other components, typically forming a combined or complementary unit within a larger whole.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 27, 2026, 2:36 p.m.