Triple
T29728577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monbazillac |
E752254
|
entity |
| Predicate | grapeDiseaseUsed |
P167816
|
FINISHED |
| Object | Botrytis cinerea |
—
|
NE NERFINISHED |
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: Botrytis cinerea | Statement: [Monbazillac, grapeDiseaseUsed, Botrytis cinerea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grapeDiseaseUsed Context triple: [Monbazillac, grapeDiseaseUsed, Botrytis cinerea]
-
A.
viticulturalUse
Indicates the way in which something is used or applied within the context of viticulture, such as grape growing or vineyard management practices.
-
B.
alsoUsesGrapeVariety
Indicates that one entity, in addition to another, makes use of the same grape variety in its composition or production.
-
C.
usesGrapeType
Indicates that one entity employs or incorporates a specific type or variety of grape in its composition, production, or process.
-
D.
usedForViticulture
Indicates that something is employed or utilized in the practice, processes, or support of viticulture (grape growing for wine production).
-
E.
grapeCondition
Indicates the state or quality of a grape, such as its health, ripeness, or any notable physical condition.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6730186988190975cd924ced4075c |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 28, 2026, 7:40 p.m.