Triple
T1776523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Softsoap liquid hand soap |
E38991
|
entity |
| Predicate | targetConsumer |
P22245
|
FINISHED |
| Object | household consumers |
—
|
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: household consumers | Statement: [Softsoap liquid hand soap, targetConsumer, household consumers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetConsumer Context triple: [Softsoap liquid hand soap, targetConsumer, household consumers]
-
A.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
B.
targetCandidate
Indicates that an entity is being considered or designated as a potential target for selection, action, or further evaluation.
-
C.
consumes
Indicates that one entity eats, drinks, or otherwise uses up another entity as a resource or nourishment.
-
D.
targetConstituency
chosen
Indicates that something is directed toward, intended for, or affects a particular constituency or group of stakeholders.
-
E.
targetVertical
Indicates that one entity is directed toward, aligned with, or intended for a specific vertical market, domain, or industry segment.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.