Triple
T1282006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spring Mountain District AVA |
E27345
|
entity |
| Predicate | wineRegionType |
P8842
|
FINISHED |
| Object | sub-appellation of Napa Valley |
—
|
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: sub-appellation of Napa Valley | Statement: [Spring Mountain District AVA, wineRegionType, sub-appellation of Napa Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineRegionType Context triple: [Spring Mountain District AVA, wineRegionType, sub-appellation of Napa Valley]
-
A.
wineRegion
Indicates the geographical region or area where a particular wine is produced or originates.
-
B.
wineRegionPartOf
chosen
Indicates that a wine-producing region is geographically or administratively contained within a larger wine region or area.
-
C.
nearWineRegion
Indicates that one entity is located close to or in the vicinity of a wine-producing region.
-
D.
appellationType
Indicates the specific kind or category of name or designation applied to an entity.
-
E.
wineClassificationSystem
Indicates a system or scheme used to categorize and organize wines based on defined criteria such as origin, style, or quality.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b317788190a1672b5ee422a049 |
completed | March 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.