Triple
T11849216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dieppe, New Brunswick |
E281863
|
entity |
| Predicate | usesMunicipalGovernmentType |
P73614
|
FINISHED |
| Object | mayor–council system |
—
|
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: mayor–council system | Statement: [Dieppe, New Brunswick, usesMunicipalGovernmentType, mayor–council system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMunicipalGovernmentType Context triple: [Dieppe, New Brunswick, usesMunicipalGovernmentType, mayor–council system]
-
A.
usesMunicipalGovernmentAct
Indicates that an entity operates under, applies, or is governed by the provisions of a Municipal Government Act.
-
B.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
C.
hasCityGovernmentType
chosen
Indicates the specific form or structure of municipal governance that administers a city.
-
D.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
E.
hasMunicipalityType
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65db52c8190a218736da17d0153 |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.