Triple
T17442213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glis |
E424683
|
entity |
| Predicate | usedToHaveMunicipalCouncil |
P127469
|
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: [Glis, usedToHaveMunicipalCouncil, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToHaveMunicipalCouncil Context triple: [Glis, usedToHaveMunicipalCouncil, yes]
-
A.
hasMunicipalCouncilUntil
Indicates that a municipal council served as the governing body of an entity up to a specified end date or point in time.
-
B.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
C.
hasMunicipalFormation
Indicates that an administrative or territorial unit is organized into, or associated with, a specific municipal formation as its local self-governing structure.
-
D.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
-
E.
hasMunicipalityWithCommissionedLocalAuthority
Indicates that a municipality is associated with a local authority to which it has formally commissioned certain administrative or governmental responsibilities.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ff82bbc819095dd0621137da809 |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:47 a.m.