Triple
T24893596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montlouis-sur-Loire AOC |
E623072
|
entity |
| Predicate | grapeVarietySynonym |
P52213
|
FINISHED |
| Object | Pineau de la Loire |
—
|
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: Pineau de la Loire | Statement: [Montlouis-sur-Loire AOC, grapeVarietySynonym, Pineau de la Loire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grapeVarietySynonym Context triple: [Montlouis-sur-Loire AOC, grapeVarietySynonym, Pineau de la Loire]
-
A.
synonymOfPrimaryGrape
chosen
Indicates that one grape variety is a synonym or alternate name for the primary grape variety specified.
-
B.
grapeVarietyScientificName
Indicates the scientific (Latin) name assigned to a specific grape variety.
-
C.
grapeVarietyType
Indicates the specific type or classification of a grape variety used or referred to in a given context.
-
D.
linkedGrapeVariety
Indicates that there is an established relationship or association between one grape variety and another (or related grape variety entity).
-
E.
alsoUsesGrapeVariety
Indicates that one entity, in addition to another, makes use of the same grape variety in its composition or production.
- 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.