Triple
T11052515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Maria Valley AVA |
E261291
|
entity |
| Predicate | AVAApprovalYear |
P24562
|
FINISHED |
| Object | 1981 |
—
|
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: 1981 | Statement: [Santa Maria Valley AVA, AVAApprovalYear, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AVAApprovalYear Context triple: [Santa Maria Valley AVA, AVAApprovalYear, 1981]
-
A.
yearApproved
Indicates the specific year in which something (such as a proposal, product, or decision) was formally approved.
-
B.
regulatoryApprovalYear
chosen
Indicates the calendar year in which an official regulatory body granted approval for the referenced item, action, or entity.
-
C.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
-
D.
accessionYear
Indicates the calendar year in which an item, record, or entity was formally added to or registered within a collection, system, or institution.
-
E.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7986c0df88190b29d71db5538450a |
completed | April 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.