Triple
T6866133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vully region |
E158405
|
entity |
| Predicate | hasViticultureTraditionSince |
P59581
|
FINISHED |
| Object | Roman times |
—
|
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: Roman times | Statement: [Vully region, hasViticultureTraditionSince, Roman times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViticultureTraditionSince Context triple: [Vully region, hasViticultureTraditionSince, Roman times]
-
A.
hasWineMakingTradition
chosen
Indicates that a place or group has an established, culturally recognized history and practice of producing wine.
-
B.
viticultureHistory
Indicates the historical development, practices, and events related to grape cultivation and winemaking over time.
-
C.
hasVineyards
Indicates that one entity possesses, contains, or is associated with vineyards used for growing grapevines.
-
D.
foundedAsVineyard
Indicates that an organization, estate, or property was originally established as a vineyard.
-
E.
hasWinemakingFacility
Indicates that an entity possesses or is associated with a facility where winemaking activities are carried out.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:21 p.m.