Triple
T22281343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipality of Carling |
E550738
|
entity |
| Predicate | countyDistrict |
P128478
|
FINISHED |
| Object | Parry Sound District |
—
|
NE NERFINISHED |
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: Parry Sound District | Statement: [Municipality of Carling, countyDistrict, Parry Sound District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countyDistrict Context triple: [Municipality of Carling, countyDistrict, Parry Sound District]
-
A.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
-
B.
governmentalDistrictOf
chosen
Indicates that a governmental district is the administrative district to which a given entity belongs or in which it is located.
-
C.
district
Indicates that one entity is an administrative or electoral district that geographically contains or governs another entity.
-
D.
majorDistrict
Indicates that one administrative district is the primary or most significant district associated with another entity or area.
-
E.
sourceDistrict
Indicates the district from which something originates, is sent, or is sourced.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14eac0994819088e39a1b5d39cf18 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.