Triple
T25057356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finch, Ontario |
E627556
|
entity |
| Predicate | hasGoverningTownship |
P145370
|
FINISHED |
| Object | North Stormont |
E606527
|
NE 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: North Stormont | Statement: [Finch, Ontario, hasGoverningTownship, North Stormont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoverningTownship Context triple: [Finch, Ontario, hasGoverningTownship, North Stormont]
-
A.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
-
B.
hasLocalGovernanceUnit
chosen
Indicates that an entity is administered or overseen by a specific local governance unit, such as a municipality, district, or similar subnational authority.
-
C.
isCivilTownship
Indicates that one entity is a civil township, i.e., an administrative or local government subdivision, in relation to another entity.
-
D.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
E.
governingTownBoard
Indicates that a town board holds governing authority or administrative control over a specified entity.
- F. None of above.
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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f459958c908190a377bb3cf34b1b28 |
completed | May 1, 2026, 7:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a105ce77d348190b7772e56a09d8836 |
completed | May 22, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:09 a.m.