Triple
T22789809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | York census division |
E564077
|
entity |
| Predicate | locatedInCensusDivisionHierarchy |
P32184
|
FINISHED |
| Object | Ontario census divisions |
—
|
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: Ontario census divisions | Statement: [York census division, locatedInCensusDivisionHierarchy, Ontario census divisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCensusDivisionHierarchy Context triple: [York census division, locatedInCensusDivisionHierarchy, Ontario census divisions]
-
A.
isInCensusDivision
chosen
Indicates that one entity (typically a geographic area or administrative unit) belongs to or is contained within a specified census division.
-
B.
isInCensusSubdivision
Indicates that one entity is located within, or falls under the jurisdiction of, a specific census subdivision.
-
C.
hasCensusSubdivision
Indicates that an entity (typically a larger administrative area) includes or is associated with a specific census-defined subdivision within it.
-
D.
locatedInRegionalDistrict
Indicates that one entity is geographically situated within the boundaries of a specified regional district.
-
E.
hasCensusDivisionCode
Indicates that an entity is associated with a specific census division identified by a particular code.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c3488708190812f7d2edac92184 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:29 p.m.