Triple
T34418725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UC Berkeley dining services |
E883469
|
entity |
| Predicate | supportsDiet |
P34157
|
FINISHED |
| Object | vegetarian diets |
—
|
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: vegetarian diets | Statement: [UC Berkeley dining services, supportsDiet, vegetarian diets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDiet Context triple: [UC Berkeley dining services, supportsDiet, vegetarian diets]
-
A.
characterizesDietAs
Indicates that one entity describes, defines, or assigns the type or nature of another entity’s diet.
-
B.
nutrientPreference
Indicates a relationship where one entity has a tendency or requirement to obtain, favor, or utilize a particular nutrient over others.
-
C.
hasPositionInDiet
Indicates the relative role or ranking that something occupies within a diet or dietary plan.
-
D.
dietaryConsideration
Indicates a relationship where one entity specifies nutritional restrictions, preferences, or requirements that should be taken into account for another entity.
-
E.
dietaryOptions
chosen
Indicates the types of diets or food-related preferences, restrictions, or choices that are applicable to or offered for an entity.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2 a.m.