Triple
T24548612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dozza |
E607293
|
entity |
| Predicate | hasWineInstitution |
P156280
|
FINISHED |
| Object | Enoteca Regionale dell’Emilia-Romagna |
—
|
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: Enoteca Regionale dell’Emilia-Romagna | Statement: [Dozza, hasWineInstitution, Enoteca Regionale dell’Emilia-Romagna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWineInstitution Context triple: [Dozza, hasWineInstitution, Enoteca Regionale dell’Emilia-Romagna]
-
A.
hasWinery
Indicates a relationship where a subject owns, operates, or is associated with a particular winery.
-
B.
hasNearbyWinery
Indicates that one entity is located close to, or in the vicinity of, a winery.
-
C.
hasWineVillage
Indicates that a place or region includes or is associated with a village known for wine production or viticulture.
-
D.
hasWinemakingFacility
Indicates that an entity possesses or is associated with a facility where winemaking activities are carried out.
-
E.
hasWineBrand
Indicates a relationship where an entity is associated with or offers a specific wine brand.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8cb6dc081909bf37123d82ed2c9 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:27 a.m.