Triple
T34237845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Bran |
E878380
|
entity |
| Predicate | targetConsumerConcern |
P64698
|
FINISHED |
| Object | constipation |
—
|
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: constipation | Statement: [All-Bran, targetConsumerConcern, constipation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetConsumerConcern Context triple: [All-Bran, targetConsumerConcern, constipation]
-
A.
targetConcern
chosen
Indicates that something is the specific issue, problem, or subject that is the focus of attention, action, or consideration.
-
B.
targetConsumerNeed
Indicates that something is intended to address, satisfy, or be directed toward a specific need or requirement of a consumer.
-
C.
subjectOfConcernFor
Indicates that one entity is regarded as a matter of worry, interest, or attention for another entity.
-
D.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
E.
scientificConcern
Indicates a relationship where one entity has a scientific worry, issue, or point of caution about another entity, typically regarding its validity, safety, impact, or implications in a scientific context.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 1, 2026, 1:56 a.m.