Triple
T18948199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahr wine region |
E463570
|
entity |
| Predicate | vineyardTraining |
P43323
|
FINISHED |
| Object | terraced vineyards |
—
|
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: terraced vineyards | Statement: [Ahr wine region, vineyardTraining, terraced vineyards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vineyardTraining Context triple: [Ahr wine region, vineyardTraining, terraced vineyards]
-
A.
typicalVineTraining
chosen
Indicates that one entity is the standard or commonly used method of training or shaping the growth of another entity, typically in a vine or climbing context.
-
B.
vineyardName
Indicates the specific name assigned to a vineyard in the relationship.
-
C.
viticulturePractice
Indicates a relationship where a specific method, technique, or practice is used in the cultivation and management of grapevines.
-
D.
acquiredVineyard
Indicates that one entity has obtained ownership or control of a vineyard from another entity or source.
-
E.
trainingModel
Indicates that an entity is engaged in the process of teaching, adjusting, or optimizing a model using data or experience.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d540e57c8190bb17fff6d4254320 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.