Triple

T32272640
Position Surface form Disambiguated ID Type / Status
Subject Mexican federal system E824454 entity
Predicate municipalAutonomyRecognized P86694 FINISHED
Object yes 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: yes | Statement: [Mexican federal system, municipalAutonomyRecognized, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: municipalAutonomyRecognized
Context triple: [Mexican federal system, municipalAutonomyRecognized, yes]
  • A. hasMunicipalRecognition
    Indicates that an entity is officially acknowledged or recognized by a municipal (city or local) government authority.
  • B. allowsMunicipalitiesTo
    Indicates that an entity grants municipalities the authority, permission, or legal capacity to perform a specified action or exercise a particular power.
  • C. servesAsMunicipalAuthorityFor
    Indicates that an entity functions as the official municipal governing or administrative authority for a specified locality or jurisdiction.
  • D. hasMunicipalGovernment
    Indicates that an entity is administered or governed by a municipal-level governmental authority.
  • E. hasLocalSelfGovernment chosen
    Indicates that an entity possesses its own local governing authority with decision-making powers over local affairs.
  • 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_69f3490e73588190915f282edd105772 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f727afd5d88190ad48735cd1b32787 completed May 3, 2026, 10:47 a.m.
PD Predicate disambiguation batch_69f72737c42c8190a3f781a5e98868ff completed May 3, 2026, 10:45 a.m.
Created at: May 1, 2026, 12:42 a.m.