Triple

T32856388
Position Surface form Disambiguated ID Type / Status
Subject Jurançon Sec E840386 entity
Predicate governingAppellation P155940 FINISHED
Object Jurançon AOC NE NERFINISHED

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: Jurançon AOC | Statement: [Jurançon Sec, governingAppellation, Jurançon AOC]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governingAppellation
Context triple: [Jurançon Sec, governingAppellation, Jurançon AOC]
  • A. overseesAppellation chosen
    Indicates that one entity has supervisory or regulatory authority over the designation or naming status of another entity.
  • B. areGovernedBy
    Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
  • C. governedInNameBy
    Indicates that one entity formally rules or administers another entity on behalf of, or under the authority or title of, a named person, group, or institution rather than in its own independent capacity.
  • D. importantAppellation
    Indicates that one entity serves as a significant or primary name, title, or designation for another entity.
  • E. governedAs
    Indicates that one entity exercises authoritative control, direction, or rule over another according to some system of governance or leadership.
  • 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_69f349412c78819084459850e11d29f7 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_6a0076c0a5c4819088b17b95511b93ed completed May 10, 2026, 12:14 p.m.
PD Predicate disambiguation batch_6a007638a67c81909c091335142260ab completed May 10, 2026, 12:12 p.m.
Created at: May 1, 2026, 1:17 a.m.