Triple
T24993210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipalities of Zacatecas |
E625500
|
entity |
| Predicate | haveGovernmentType |
P130835
|
FINISHED |
| Object | municipal council |
—
|
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: municipal council | Statement: [Municipalities of Zacatecas, haveGovernmentType, municipal council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveGovernmentType Context triple: [Municipalities of Zacatecas, haveGovernmentType, municipal council]
-
A.
hasGovernmentTypeCountry
Indicates that a country possesses or is characterized by a particular form or type of government.
-
B.
hasGovernmentalBodyType
chosen
Indicates the specific kind or classification of governmental body that an entity possesses or is associated with.
-
C.
governmentType
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
D.
hasGovernmentBody
Indicates that one entity serves as the official governing or administrative body responsible for overseeing or managing another entity.
-
E.
governmentTypeSupported
Indicates that an entity endorses, backs, or is in favor of a particular form or system of government.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44a4787948190874b230f692d16c7 |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:04 a.m.