Triple

T37067740
Position Surface form Disambiguated ID Type / Status
Subject Opglabbeek E917493 entity
Predicate hasMunicipalFusionPartner P197615 FINISHED
Object Meeuwen-Gruitrode 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: Meeuwen-Gruitrode | Statement: [Opglabbeek, hasMunicipalFusionPartner, Meeuwen-Gruitrode]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMunicipalFusionPartner
Context triple: [Opglabbeek, hasMunicipalFusionPartner, Meeuwen-Gruitrode]
  • A. hasMunicipalPartnershipWith
    Indicates a formal cooperative or collaborative relationship established between two municipalities, typically involving shared projects, services, or governance initiatives.
  • B. hasCityPartner
    Indicates that two cities are formally linked through a partnership, such as a sister-city or twinning relationship.
  • C. hasPartner
    Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
  • D. hasPartnerOrganization
    Indicates that an entity is formally associated or collaborates with another entity as a partner organization.
  • E. hasJointVenturePartner
    Indicates that an entity is engaged in a joint venture relationship with another entity as a formal business partner.
  • F. None of above. chosen

Provenance (4 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_69f76e95fa40819091e14681087ae5e4 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fe9dfaa2d08190b2084f63f842eb6b completed May 9, 2026, 2:37 a.m.
PD Predicate disambiguation batch_69fe9bba947c81908b0b2b92a4d19b37 completed May 9, 2026, 2:28 a.m.
PDg Predicate description generation batch_69fe9df9561c8190a068f91c9fc78e56 completed May 9, 2026, 2:37 a.m.
Created at: May 3, 2026, 4:14 p.m.