Triple
T5421044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Nipissing (southern portion) |
E121249
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subdivision of district |
C18084
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: subdivision of district Context triple: [District of Nipissing (southern portion), instanceOf, subdivision of district]
-
A.
subdivision of a district in India
A subdivision of a district in India is an administrative unit below the district level that groups several tehsils or blocks to facilitate local governance, revenue administration, and public service delivery.
-
B.
regulatory subdivision
A regulatory subdivision is a defined geographic or administrative area within a jurisdiction established for the purpose of applying, enforcing, or managing specific regulations, policies, or legal requirements.
-
C.
township-level division
A township-level division is a local administrative unit within a country, typically governing a small urban or rural area below the county level and responsible for basic public services and local governance.
-
D.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
E.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
- F. None of above. chosen
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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:06 p.m.