Triple
T15472742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fig Newtons |
E376703
|
entity |
| Predicate | hasNutritionalRole |
P110628
|
FINISHED |
| Object | energy-dense snack |
—
|
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: energy-dense snack | Statement: [Fig Newtons, hasNutritionalRole, energy-dense snack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNutritionalRole Context triple: [Fig Newtons, hasNutritionalRole, energy-dense snack]
-
A.
hasNutrientStatus
Indicates that an entity possesses a particular nutritional condition or level, such as being deficient, sufficient, or excessive in specific nutrients.
-
B.
hasPositionInDiet
chosen
Indicates the relative role or ranking that something occupies within a diet or dietary plan.
-
C.
biologicalRole
Indicates the functional role or purpose that one biological entity has in relation to another or within a biological process.
-
D.
nutritionMode
Indicates the way an entity obtains or processes nutrients for sustenance or growth.
-
E.
hasNutrientContent
Indicates that one entity contains or provides a specified amount or type of nutrient relative to another entity or standard.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6c57308190b4cfe661c26addd4 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.