Triple
T34824193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conero |
E1003869
|
entity |
| Predicate | isInWineZone |
P159942
|
FINISHED |
| Object | Central Italy |
—
|
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: Central Italy | Statement: [Conero, isInWineZone, Central Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInWineZone Context triple: [Conero, isInWineZone, Central Italy]
-
A.
isInWineOrBeerRegion
Indicates that something is located within a geographic area known for producing wine or beer.
-
B.
isInWineOrSpiritsRegion
chosen
Indicates that one entity (typically a location or product) is situated within or associated with a designated wine or spirits-producing region of another entity.
-
C.
isSingleVineyardWine
Indicates that the wine comes exclusively from grapes grown in a single, specific vineyard.
-
D.
includesWineProvince
Indicates that one entity (typically a region or collection) contains or encompasses a specific wine-producing province within its scope.
-
E.
wineZoneStatus
Indicates the status or condition of a designated wine-related zone or area in relation to a given context or system.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77adf71d88190812e930bcf1e2ce5 |
completed | May 3, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 4 p.m.