Triple
T2180869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Médoc |
E49037
|
entity |
| Predicate | viticulturalActivity |
P17952
|
FINISHED |
| Object | viticulture |
—
|
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: viticulture | Statement: [Médoc, viticulturalActivity, viticulture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viticulturalActivity Context triple: [Médoc, viticulturalActivity, viticulture]
-
A.
viticulturePractice
Indicates a relationship where a specific method, technique, or practice is used in the cultivation and management of grapevines.
-
B.
viticulturalFocus
chosen
Indicates a focus on or specialization in viticulture, i.e., activities, practices, or interests centered on grape growing and vineyard management.
-
C.
viticulturalCharacteristic
Indicates a relationship where a specific trait, quality, or property is attributed to viticulture or grape-growing practices.
-
D.
viticulturalChallenge
Indicates a relationship where one party faces or presents a difficulty, problem, or obstacle specifically related to grape growing or vineyard management.
-
E.
wineGrapesCultivated
Indicates that certain grape varieties are grown or cultivated specifically for producing wine.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc4358fc88190a6f556c2de9fef8c |
completed | March 7, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69abbda0ec948190be88c1243d81a423 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.