Triple

T16476259
Position Surface form Disambiguated ID Type / Status
Subject Cornish pasty E400193 entity
Predicate PGIRequirement P90447 FINISHED
Object must be produced in Cornwall 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: must be produced in Cornwall | Statement: [Cornish pasty, PGIRequirement, must be produced in Cornwall]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: PGIRequirement
Context triple: [Cornish pasty, PGIRequirement, must be produced in Cornwall]
  • A. evaluationRequirement
    Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
  • B. packagingRequirement
    Indicates the specific conditions, standards, or constraints that must be met in how something is packaged.
  • C. policyRequirement chosen
    Indicates that one entity specifies a rule, condition, or obligation that another entity must satisfy according to a policy.
  • D. dialogRequirement
    Indicates that a certain condition, piece of information, or interaction must occur within a dialog or conversation for a related action, state, or process to proceed or be considered valid.
  • E. proceduralRequirement
    Indicates that one entity specifies or imposes a required procedure or process that must be followed by another entity.
  • 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_69d883813098819084f5409539723b59 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32dd4f53081908f78b88435c8c719 completed April 18, 2026, 7:08 a.m.
PD Predicate disambiguation batch_69e22706b0588190a48a951c5211a617 completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:13 a.m.