Triple
T21988498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magna Meadows at Magnetic Hill |
E543022
|
entity |
| Predicate | governingJurisdiction |
P6400
|
FINISHED |
| Object | City of Moncton municipal government |
—
|
NE GENERATED |
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: City of Moncton municipal government Context triple: [Magna Meadows at Magnetic Hill, governingJurisdiction, City of Moncton municipal government]
-
A.
Moncton City Council
chosen
Moncton City Council is the municipal governing body responsible for setting policies, passing bylaws, and overseeing local services and development in the city of Moncton, New Brunswick.
-
B.
Fredericton City Council
Fredericton City Council is the municipal governing body responsible for setting policies, passing bylaws, and overseeing local services in the city of Fredericton, New Brunswick, Canada.
-
C.
Greater Moncton metropolitan area
The Greater Moncton metropolitan area is a major urban and economic hub in southeastern New Brunswick, Canada, centered on the city of Moncton and its surrounding communities.
-
D.
City of New Brunswick municipal government
The City of New Brunswick municipal government is the local governing body responsible for administering public services, regulations, and development for New Brunswick, New Jersey.
-
E.
Government of New Brunswick
The Government of New Brunswick is the provincial authority responsible for administering public services, laws, and policies within the Canadian province of New Brunswick.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8:05 p.m.