Triple

T489003
Position Surface form Disambiguated ID Type / Status
Subject Stags Leap District AVA E9943 entity
Predicate regulatoryType P14058 FINISHED
Object appellation of origin 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: appellation of origin | Statement: [Stags Leap District AVA, regulatoryType, appellation of origin]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatoryType
Context triple: [Stags Leap District AVA, regulatoryType, appellation of origin]
  • A. worksOnRegulationType
    Indicates that an entity is involved in work or activities related to a specific type or category of regulation.
  • B. regulatoryOutcome
    Indicates the result or consequence of a regulatory process, such as approval, rejection, modification, or other formal decision made by a regulatory authority regarding an entity or action.
  • C. regulatoryDomain
    Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
  • D. governedByLegalRegime
    Indicates that an entity is subject to, regulated by, or operating under a specific legal framework or set of legal rules.
  • E. typeOfLegislation
    Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
  • F. None of above. chosen

Provenance (4 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_69a2e802e2908190ab17c9479e0b6412 completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2f0df764481909811d9483dfbc4aa completed Feb. 28, 2026, 1:42 p.m.
PD Predicate disambiguation batch_69a2edf63fbc819090ea6ca11f39116a completed Feb. 28, 2026, 1:30 p.m.
PDg Predicate description generation batch_69a2eebb2c908190960a4d0c014304cd completed Feb. 28, 2026, 1:33 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.