Triple
T23175858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morris of Rutherglen |
E579000
|
entity |
| Predicate | hasWinemakingHeritage |
P59581
|
FINISHED |
| Object | multi‑generation family winemaking tradition |
—
|
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: multi‑generation family winemaking tradition | Statement: [Morris of Rutherglen, hasWinemakingHeritage, multi‑generation family winemaking tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWinemakingHeritage Context triple: [Morris of Rutherglen, hasWinemakingHeritage, multi‑generation family winemaking tradition]
-
A.
hasWineMakingTradition
chosen
Indicates that a place or group has an established, culturally recognized history and practice of producing wine.
-
B.
hasWinemakingFacility
Indicates that an entity possesses or is associated with a facility where winemaking activities are carried out.
-
C.
hasWinery
Indicates a relationship where a subject owns, operates, or is associated with a particular winery.
-
D.
producesWine
Indicates that one entity creates or manufactures wine as a product.
-
E.
hasVineyards
Indicates that one entity possesses, contains, or is associated with vineyards used for growing grapevines.
- 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f6a8644819099b107bb13ea16ff |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:04 p.m.