Triple

T13436193
Position Surface form Disambiguated ID Type / Status
Subject Niçois (dialecte) E320234 entity
Predicate zonePériurbaine P73839 FINISHED
Object arrière-pays niçois 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: arrière-pays niçois | Statement: [Niçois (dialecte), zonePériurbaine, arrière-pays niçois]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: zonePériurbaine
Context triple: [Niçois (dialecte), zonePériurbaine, arrière-pays niçois]
  • A. hasArrondissement
    Indicates a relationship where an administrative unit or locality is associated with, or belongs to, a specific arrondissement.
  • B. hasCommunesNear
    Indicates that one entity has communes located in its nearby geographic vicinity.
  • C. hasUrbanAgglomeration chosen
    Indicates that an entity includes, is associated with, or is characterized by a specific urban agglomeration (a densely populated urban area and its surrounding zones).
  • D. hasCommune
    Indicates a relationship where an entity is associated with, belongs to, or is located within a specific commune (municipal administrative unit).
  • E. inseeCode
    Indicates the official INSEE (French national statistics institute) code assigned to an entity, typically identifying a specific geographic or administrative unit.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaee42a8c8190a85716b4a6db335e completed April 12, 2026, 2:40 p.m.
PD Predicate disambiguation batch_69d9a03926188190ab3948d1f5d3941f completed April 11, 2026, 1:13 a.m.
Created at: April 9, 2026, 9:40 p.m.