Triple
T36443532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coffea |
E897801
|
entity |
| Predicate | roleInDiet |
P203479
|
FINISHED |
| Object | source of one of the most widely consumed beverages |
—
|
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: source of one of the most widely consumed beverages | Statement: [Coffea, roleInDiet, source of one of the most widely consumed beverages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDiet Context triple: [Coffea, roleInDiet, source of one of the most widely consumed beverages]
-
A.
roleInFood
Indicates the functional role or purpose that an entity has within a food item, product, or context (e.g., ingredient, flavoring, preservative).
-
B.
roleInFoodInc
Indicates that an entity holds a specific role or position within the organization or context referred to as FoodInc.
-
C.
characterizesDietAs
Indicates that one entity describes, defines, or assigns the type or nature of another entity’s diet.
-
D.
dietVersion
Indicates that one diet is a specific version, variant, or iteration of another diet.
-
E.
hasPositionInDiet
Indicates the relative role or ranking that something occupies within a diet or dietary plan.
- F. None of above. chosen
Provenance (4 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a018c6b7178819097d5450a1e3c2408 |
completed | May 11, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_6a018a4f741c8190babe721a908e2f5e |
completed | May 11, 2026, 7:50 a.m. |
| PDg | Predicate description generation | batch_6a018c6aaca081908c63d8d624fe9ec4 |
completed | May 11, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:10 p.m.