Triple
T34238052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Grains |
E878385
|
entity |
| Predicate | healthPositioning |
P109970
|
FINISHED |
| Object | wholesome ingredients |
—
|
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: wholesome ingredients | Statement: [Great Grains, healthPositioning, wholesome ingredients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthPositioning Context triple: [Great Grains, healthPositioning, wholesome ingredients]
-
A.
positionOnHealthCare
Indicates a person or entity’s stance, opinion, or policy preference regarding health care systems, services, or reforms.
-
B.
healthTheme
chosen
Indicates that the subject is associated with, focuses on, or is characterized by a particular health-related topic or theme.
-
C.
healthSystem
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
D.
healthServiceProvider
Indicates that one entity provides health-related services or care to another entity.
-
E.
healthRationale
Indicates the reasoning or justification behind an assessment, decision, or action related to health.
- 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_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:56 a.m.