Triple
T28661597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunnic rule in Pannonia |
E725481
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | history of Pannonia |
C14422
|
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: history of Pannonia Context triple: [Hunnic rule in Pannonia, instanceOf, history of Pannonia]
-
A.
history of Hungary
The history of Hungary traces the evolution of the Hungarian people and state from early migrations and the founding of the medieval kingdom through Ottoman and Habsburg rule, the World Wars and communist era, to its modern democratic identity within Europe.
-
B.
history of Hungary
The history of Hungary traces the evolution of the Hungarian people and state from early Magyar migrations and the founding of the medieval kingdom through Ottoman and Habsburg rule, the Austro-Hungarian Empire, 20th-century wars and communism, to its modern democratic republic within the European Union.
-
C.
history of a region
chosen
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.
Romani history
Romani history traces the migration, persecution, resilience, and cultural evolution of the Romani people from their origins in the Indian subcontinent to their diverse diasporic communities across Europe and beyond.
-
E.
history of Poland
The history of Poland traces the development of the Polish state and nation from its early medieval origins through partitions, independence struggles, world wars, communist rule, and modern democratic transformation.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:58 a.m.