Triple
T19290184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Districts of Haryana |
E482420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division collection |
C41870
|
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: administrative division collection Context triple: [Districts of Haryana, instanceOf, administrative division collection]
-
A.
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.
-
B.
administrative division of Japan
An administrative division of Japan is a geographically defined area, such as a prefecture, municipality, or special ward, established by the government to organize local governance, public administration, and the delivery of services.
-
C.
province-level administrative division
A province-level administrative division is a primary subnational territorial unit within a country, governed by its own regional authorities under the framework of the national government.
-
D.
census division
A census division is a geographic area defined by a government statistical agency for the purpose of collecting, organizing, and analyzing population and demographic data.
-
E.
administrative division of France
An administrative division of France is a territorial unit, such as a region, department, arrondissement, canton, or commune, established by the French government to organize local governance, public administration, and the delivery of state services.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:30 p.m.