Triple
T21279113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machanshyre |
E524470
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical territorial division |
C536
|
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 division Context triple: [Machanshyre, instanceOf, historical territorial division]
-
A.
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.
-
B.
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.
-
C.
history of a region
A history of a region is a structured account of the social, political, economic, and cultural developments that have shaped a specific geographic area over time.
-
D.
historical polities
Historical polities are organized political entities or governing structures that existed in the past, such as kingdoms, empires, city-states, and federations, defined by their territorial control, institutions, and sociopolitical systems.
-
E.
former administrative territorial entity
chosen
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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:02 p.m.