Triple
T22000152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Projet Montréal |
E543302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | municipal political party |
C45648
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: municipal political party Context triple: [Projet Montréal, instanceOf, municipal political party]
-
A.
municipal political organization leadership
Municipal political organization leadership encompasses the individuals and structures responsible for guiding, coordinating, and representing a city or town’s political party activities, strategies, and community engagement at the local level.
-
B.
municipal organization
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
-
C.
municipal election
A municipal election is a local voting process in which residents choose representatives and decide on issues that govern a city, town, or other local jurisdiction.
-
D.
municipality
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
-
E.
municipal government committee
A municipal government committee is a formally organized group within a local government tasked with studying specific issues, advising the city or town council, and sometimes making decisions or recommendations on policies, services, and regulations affecting the community.
- F. None of above. chosen
Provenance (1 batch)
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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:20 p.m.