Triple
T15182396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire of Alexander the Great |
E362777
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Macedonian empire |
C4987
|
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: Macedonian empire Context triple: [Empire of Alexander the Great, instanceOf, Macedonian empire]
-
A.
Bulgar state
A Bulgar state is a political entity historically founded and ruled by the Bulgar people, typically characterized by a semi-nomadic warrior elite governing settled agricultural populations within a defined territory.
-
B.
Eastern Roman Empire
The Eastern Roman Empire, also known as the Byzantine Empire, was the continuation of the Roman Empire in its eastern provinces, centered on Constantinople, that preserved Roman governance, law, and culture while developing a distinct Greek-speaking Christian civilization from late antiquity through the Middle Ages.
-
C.
ancient empire
chosen
An ancient empire is a large, centralized civilization from antiquity that exerts political, military, economic, and cultural control over diverse territories and peoples under a single dominant authority.
-
D.
Macedonian king
A Macedonian king is a sovereign ruler of the ancient kingdom of Macedonia, wielding military, political, and religious authority over its territories and people.
-
E.
Eurasian empire
A Eurasian empire is a vast, centralized political entity that spans significant territories across both Europe and Asia, integrating diverse cultures, economies, and governance systems under a single imperial authority.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:09 a.m.