Triple
T11421640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pfalz |
E270634
|
entity |
| Predicate | regulatesWineProductionUnder |
P41067
|
FINISHED |
| Object | German wine law |
—
|
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: German wine law | Statement: [Pfalz, regulatesWineProductionUnder, German wine law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesWineProductionUnder Context triple: [Pfalz, regulatesWineProductionUnder, German wine law]
-
A.
regulatesWineType
Indicates that one entity has authority or influence over the rules, standards, or conditions governing a particular type of wine.
-
B.
redWineProductionAllowed
Indicates that producing red wine is permitted under the relevant rules, conditions, or regulations.
-
C.
whiteWineProductionAllowed
Indicates that producing white wine is permitted under the relevant rules, regulations, or conditions.
-
D.
producesWine
Indicates that one entity creates or manufactures wine as a product.
-
E.
wineRegulationBody
chosen
Indicates that a regulatory organization has authority over the production, labeling, or distribution standards for a particular wine or wine-producing region.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b357e88190ace56d36a945688f |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.