Triple
T17620036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stikine Region |
E429685
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional district-level subdivision |
C29804
|
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: regional district-level subdivision Context triple: [Stikine Region, instanceOf, regional district-level subdivision]
-
A.
subdivision of district
A subdivision of district is an administrative unit that forms a smaller, constituent part of a larger district within a governmental or organizational hierarchy.
-
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.
third-tier administrative subdivision
A third-tier administrative subdivision is a local governmental unit that operates below the second-tier division within a country's hierarchical administrative structure, typically managing community-level services and regulations.
-
D.
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.
-
E.
Second-level administrative division
chosen
A second-level administrative division is a territorial unit within a country that is directly below the primary (first-level) administrative regions, such as provinces or states, and typically manages local governance and public services.
- F. None of above.
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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:51 a.m.