Triple
T27017035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richebourg |
E680562
|
entity |
| Predicate | allowedGrape |
P37246
|
FINISHED |
| Object | Pinot Noir |
—
|
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: Pinot Noir | Statement: [Richebourg, allowedGrape, Pinot Noir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedGrape Context triple: [Richebourg, allowedGrape, Pinot Noir]
-
A.
grapeVarietyAllowed
chosen
Indicates that a specific grape variety is permitted or authorized for use in a given context, such as a wine, region, or product specification.
-
B.
usesGrapeType
Indicates that one entity employs or incorporates a specific type or variety of grape in its composition, production, or process.
-
C.
grapeCondition
Indicates the state or quality of a grape, such as its health, ripeness, or any notable physical condition.
-
D.
grapeSourceFlexibility
Indicates that the source or origin of grapes involved in a relationship or process can vary or be chosen flexibly rather than being fixed.
-
E.
hasRegulatedGrapes
Indicates that certain grapes are subject to specific rules, standards, or controls imposed by an authority or regulation.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 7:06 a.m.