Triple
T22852966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boknal |
E566399
|
entity |
| Predicate | healthBelief |
P75621
|
FINISHED |
| Object | hot, nutritious food helps endure heat |
—
|
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: hot, nutritious food helps endure heat | Statement: [Boknal, healthBelief, hot, nutritious food helps endure heat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthBelief Context triple: [Boknal, healthBelief, hot, nutritious food helps endure heat]
-
A.
healthTheme
Indicates that the subject is associated with, focuses on, or is characterized by a particular health-related topic or theme.
-
B.
healthRationale
chosen
Indicates the reasoning or justification behind an assessment, decision, or action related to health.
-
C.
relatedBelief
Indicates that one belief is connected to, derived from, or otherwise associated with another belief in some meaningful way.
-
D.
healthResponsibility
Indicates that an entity has a duty or obligation to maintain, protect, or manage the health or well-being of another entity or itself.
-
E.
healthAssociation
Indicates a relationship where one factor, condition, or entity is linked to an effect, outcome, or status 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eba65a881908c484262c3ee5212 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.