Triple
T27649835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balharshah tehsil of Telangana (historical association) |
E696818
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical territorial association |
C20214
|
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: historical territorial association Context triple: [Balharshah tehsil of Telangana (historical association), instanceOf, historical territorial association]
-
A.
territorial relationship
chosen
A territorial relationship is a conceptual association that defines how entities claim, control, share, or interact within a specific geographic or spatial area.
-
B.
historical geographic entity
A historical geographic entity is a spatially bounded area whose location, extent, or political status has changed or ceased to exist over time, but which is recognized for its past geographic or administrative significance.
-
C.
historical alliance
A historical alliance is a formal or informal partnership between states, groups, or leaders formed in the past to pursue shared political, military, economic, or cultural goals.
-
D.
pre-colonial territory
A pre-colonial territory is a geographically defined area governed, used, or inhabited by indigenous or local societies before the imposition of foreign colonial rule and boundaries.
-
E.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:31 p.m.