Triple
T24893621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montlouis-sur-Loire AOC |
E623072
|
entity |
| Predicate | botrytisPotential |
P144471
|
FINISHED |
| Object | yes, in suitable vintages |
—
|
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: yes, in suitable vintages | Statement: [Montlouis-sur-Loire AOC, botrytisPotential, yes, in suitable vintages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: botrytisPotential Context triple: [Montlouis-sur-Loire AOC, botrytisPotential, yes, in suitable vintages]
-
A.
usesBotrytisCinerea
Indicates that an entity employs or applies the fungus *Botrytis cinerea* (e.g., as a tool, agent, or method) in carrying out some process or activity.
-
B.
respondsToBotrytis
chosen
Indicates that an entity exhibits a reaction or response to the presence or effects of Botrytis (a fungal pathogen).
-
C.
yeastPresence
Indicates that yeast is present or detected in relation to the specified entity or context.
-
D.
containsMycotoxinProducers
Indicates that the subject includes or encompasses entities that produce mycotoxins.
-
E.
mustBeFermentedBy
Indicates that one entity is required to undergo a fermentation process carried out by another specified 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_69e2fac597708190a922bf39a49ec70a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:26 a.m.