Triple
T28531252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milk |
E722046
|
entity |
| Predicate | dietaryRole |
P129066
|
FINISHED |
| Object | Staple food in many cultures |
—
|
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: Staple food in many cultures | Statement: [Milk, dietaryRole, Staple food in many cultures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dietaryRole Context triple: [Milk, dietaryRole, Staple food in many cultures]
-
A.
roleInFood
chosen
Indicates the functional role or purpose that an entity has within a food item, product, or context (e.g., ingredient, flavoring, preservative).
-
B.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
C.
dietAdvocated
Indicates that one entity promotes, recommends, or supports a particular diet for another entity or audience.
-
D.
nutritionStandard
Indicates that something complies with, or is evaluated against, a defined set of nutritional guidelines or requirements.
-
E.
characterizesDietAs
Indicates that one entity describes, defines, or assigns the type or nature of another entity’s diet.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 3:28 a.m.