Triple
T27761693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maindreieck |
E701485
|
entity |
| Predicate | wineBottleTradition |
P163225
|
FINISHED |
| Object | Bocksbeutel |
—
|
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: Bocksbeutel | Statement: [Maindreieck, wineBottleTradition, Bocksbeutel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineBottleTradition Context triple: [Maindreieck, wineBottleTradition, Bocksbeutel]
-
A.
nationalWineTradition
Indicates that a country or region has an established cultural and historical practice of producing, consuming, and valuing wine.
-
B.
wineLaw
Indicates a legal or regulatory relationship governing the production, sale, labeling, or distribution of wine.
-
C.
wineStructure
Indicates the overall sensory framework of a wine, encompassing how its components like acidity, tannin, body, and alcohol are balanced and interact.
-
D.
traditionalWineChoice
Indicates that an entity selects or prefers a wine option that aligns with customary or historically established pairing or serving practices.
-
E.
sharesWineAndBeerCulture
Indicates that two entities have a common cultural tradition or practice involving both wine and beer.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6376620888190bade1617f8c45ba1 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 4:27 p.m.