Triple

T32079916
Position Surface form Disambiguated ID Type / Status
Subject deelgemeente E819265 entity
Predicate equivalentTermInFrench P156673 FINISHED
Object section de commune 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: section de commune | Statement: [deelgemeente, equivalentTermInFrench, section de commune]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: equivalentTermInFrench
Context triple: [deelgemeente, equivalentTermInFrench, section de commune]
  • A. equivalentTitleInFrench
    Indicates that one entity’s title is the equivalent or corresponding title of another entity, specifically expressed in French.
  • B. cognateInFrench chosen
    Indicates that a given word has a corresponding French word with a common etymological origin and similar form or meaning.
  • C. isFrancophoneCounterpartOf
    Indicates that one entity serves as the French-speaking or French-language equivalent or counterpart of another entity.
  • D. correspondsToAbbreviationInFrench
    Indicates that one entity is the full form or expression for which the other entity serves as the abbreviation in French.
  • E. equivalentIn
    Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
  • 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_69f348ff8ef88190931c08ba530a36bc completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6db6af1d88190989810182354d60f completed May 3, 2026, 5:21 a.m.
PD Predicate disambiguation batch_69f6d82d068c8190940a3200ed760e38 completed May 3, 2026, 5:07 a.m.
Created at: May 1, 2026, 12:24 a.m.