Triple

T32532240
Position Surface form Disambiguated ID Type / Status
Subject Tongrinne E831485 entity
Predicate municipalSectionOf P85342 FINISHED
Object Sombreffe 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: Sombreffe | Statement: [Tongrinne, municipalSectionOf, Sombreffe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: municipalSectionOf
Context triple: [Tongrinne, municipalSectionOf, Sombreffe]
  • A. isMunicipalSectorOf chosen
    Indicates that one entity is a municipal-level subdivision, department, or sector that forms part of the organizational structure of another entity (typically a municipality or local government).
  • B. hasMunicipalSections
    Indicates that a municipality is divided into and associated with specific internal administrative sections or districts.
  • C. hasMunicipalPart
    Indicates that an administrative or territorial entity includes a municipality as one of its constituent parts.
  • D. servesAsMunicipalAuthorityFor
    Indicates that an entity functions as the official municipal governing or administrative authority for a specified locality or jurisdiction.
  • E. municipalKey
    Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
  • 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_69f34924b1cc8190ad3aca0c0f012a7e completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f72921cf2c8190909bb53f78bcc890 completed May 3, 2026, 10:53 a.m.
PD Predicate disambiguation batch_69f7283d8cec8190b524c144948bc4ec completed May 3, 2026, 10:49 a.m.
Created at: May 1, 2026, 1:01 a.m.