Triple
T37248709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medieval Central Europe |
E923933
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical period in Europe |
C138
|
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 period in Europe Context triple: [Medieval Central Europe, instanceOf, historical period in Europe]
-
A.
historical period
chosen
A historical period is a span of time characterized by distinct social, political, cultural, or technological conditions that differentiate it from other eras in history.
-
B.
era of European colonialism
The era of European colonialism was a historical period from roughly the 15th to the early 20th century during which European powers explored, conquered, and exploited vast regions across the globe, reshaping political, economic, social, and cultural structures worldwide.
-
C.
region of Europe
A region of Europe is a geographically or culturally defined area within the European continent that shares common physical, historical, political, or socio-economic characteristics distinguishing it from other areas.
-
D.
historical city period
A historical city period is a span of time in a city's past characterized by distinctive social, political, economic, and cultural conditions that shape its development and identity.
-
E.
historical period in Western art music
A historical period in Western art music is a span of time characterized by relatively distinct and shared stylistic, aesthetic, and compositional practices among composers and performers within the Western classical tradition.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.