Triple
T6942210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life Plankton line |
E160704
|
entity |
| Predicate | targetBenefit |
P49949
|
FINISHED |
| Object | skin regeneration |
—
|
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: skin regeneration | Statement: [Life Plankton line, targetBenefit, skin regeneration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetBenefit Context triple: [Life Plankton line, targetBenefit, skin regeneration]
-
A.
primaryBenefit
Indicates that one entity serves as the main or most important advantage, gain, or positive outcome associated with another entity.
-
B.
expectedBenefit
chosen
Indicates the benefit or positive outcome that is anticipated to result from a particular action, decision, or relationship between entities.
-
C.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
D.
believedBenefit
Indicates that one entity considers or perceives another entity, action, or state as providing an advantage or positive outcome.
-
E.
benefits
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.