Triple
T37329367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thuringian-Saxon area |
E926699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical territorial region |
C263
|
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 region Context triple: [Thuringian-Saxon area, instanceOf, historical territorial region]
-
A.
ancient territory
An ancient territory is a historically defined geographic region that was controlled, inhabited, or claimed by past civilizations or cultures, often with distinct political, cultural, or religious significance.
-
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.
historic region
chosen
A historic region is a geographically defined area recognized for its significant past events, cultural heritage, or historical identity that has shaped its development over time.
-
D.
historical region of Russia
A historical region of Russia is a geographically defined area within the Russian state or its predecessor entities that possesses a distinct historical, cultural, and often administrative identity shaped by past events, peoples, and political 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.