Triple

T35822057
Position Surface form Disambiguated ID Type / Status
Subject Avignon Regional County Municipality E1035529 entity
Predicate hasRegionalCountyMunicipalityCode P3943 FINISHED
Object 06 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: 06 | Statement: [Avignon Regional County Municipality, hasRegionalCountyMunicipalityCode, 06]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegionalCountyMunicipalityCode
Context triple: [Avignon Regional County Municipality, hasRegionalCountyMunicipalityCode, 06]
  • A. hasMunicipalityCode chosen
    Indicates that an entity is associated with a specific official municipality code used for administrative or identification purposes.
  • B. hasCountyCode
    Indicates that an entity is associated with a specific county identified by a standardized county code.
  • C. isRegionalCountyMunicipalityEquivalent
    Indicates that one administrative unit has the same legal or functional status as a regional county municipality within a given jurisdiction.
  • D. hasCountyCodeType
    Indicates that an entity is associated with a specific type or classification of county code.
  • E. hasMunicipalCodeArea
    Indicates that a municipality is associated with a specific administrative or statistical area defined by a municipal code.
  • 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_69f76e185ffc8190880b3cdf51decd38 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_6a037ce70f54819082946dad8d380825 completed May 12, 2026, 7:17 p.m.
PD Predicate disambiguation batch_6a037a069e6c8190857b611fffb7b867 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:06 p.m.