Triple
T9175478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fresno State Winery |
E220188
|
entity |
| Predicate | offersExperienceIn |
P48639
|
FINISHED |
| Object | grape processing |
—
|
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: grape processing | Statement: [Fresno State Winery, offersExperienceIn, grape processing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersExperienceIn Context triple: [Fresno State Winery, offersExperienceIn, grape processing]
-
A.
recommendedExperience
Indicates that a certain level or type of prior experience is advised or preferred for engaging in the related activity, role, or item.
-
B.
offersExperientialLearning
chosen
Indicates that one entity provides another with hands-on, practical learning opportunities gained through direct experience.
-
C.
offersDiscipline
Indicates that one entity provides or makes available a particular field of study, training, or area of specialization to another entity.
-
D.
experiences
Indicates that an entity undergoes, feels, or is affected by a particular event, state, or condition.
-
E.
experienceType
Indicates the specific kind or category of experience associated with an entity or event.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccbfa496548190a096969eebf732f3 |
completed | April 1, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.