Triple
T20762758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipality of Leamington |
E511012
|
entity |
| Predicate | provincialCode |
P99880
|
FINISHED |
| Object | ON |
—
|
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: ON | Statement: [Municipality of Leamington, provincialCode, ON]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: provincialCode Context triple: [Municipality of Leamington, provincialCode, ON]
-
A.
hasProvincialCode
chosen
Indicates that an entity is associated with a specific provincial code that identifies its province or administrative region.
-
B.
baseProvince
Indicates that one administrative or territorial unit serves as the primary or originating province associated with another entity.
-
C.
isProvincial
Indicates that something belongs to, is characteristic of, or is administered at the level of a province rather than a national or local level.
-
D.
adminProvince
Indicates that one entity serves as the administrative province or primary provincial jurisdiction for another entity.
-
E.
hasPrefecturalCode
Indicates that an entity is associated with a specific prefectural identification code assigned by an administrative system.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24a154c8190a9062923308d2411 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:35 p.m.