Triple

T8045208
Position Surface form Disambiguated ID Type / Status
Subject Orvieto Classico E187529 entity
Predicate classicoZone P80718 FINISHED
Object historic core of Orvieto production area 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: historic core of Orvieto production area | Statement: [Orvieto Classico, classicoZone, historic core of Orvieto production area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: classicoZone
Context triple: [Orvieto Classico, classicoZone, historic core of Orvieto production area]
  • A. consideredClassic
    Indicates that something is widely regarded or recognized as a classic within a particular field, genre, or context.
  • B. formerZone
    Indicates that an entity was previously designated as a particular zone or area but no longer holds that status.
  • C. numberInClassicalTradition
    Indicates that an entity is associated with a specific number as defined or used within a particular classical tradition (e.g., mythology, religion, or philosophy).
  • D. typicalChamber
    Indicates that something is a standard or characteristic chamber associated with a given context or entity.
  • E. wonMonumentClassic
    Indicates that an entity achieved victory in a cycling Monument classic race.
  • 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_69ca82b00cb48190b59a300f70e97bd7 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3f4c79388190aecee6e313071a17 completed March 31, 2026, 3:28 a.m.
PD Predicate disambiguation batch_69cb049688208190b32088bd2c5930bc completed March 30, 2026, 11:17 p.m.
PDg Predicate description generation batch_69cb14bcbbc0819094a98e7ffffb7a40 completed March 31, 2026, 12:26 a.m.
Created at: March 30, 2026, 5:24 p.m.