Triple
T19823460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Alexandria (168 BCE) |
E476256
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Hellenistic history |
C37598
|
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: event in Hellenistic history Context triple: [Siege of Alexandria (168 BCE), instanceOf, event in Hellenistic history]
-
A.
event in ancient history
An event in ancient history is a significant occurrence or series of actions that took place in early human civilizations and has had a lasting impact on cultural, political, or social development.
-
B.
Hellenistic-period conflict
chosen
A Hellenistic-period conflict is a military or political struggle occurring between Alexander the Great’s death in 323 BCE and the Roman conquest of the eastern Mediterranean, typically involving successor kingdoms vying for territory, power, and influence.
-
C.
Hellenistic institution
A Hellenistic institution is an organized social, political, religious, or educational structure that developed or operated within the culturally blended Greek-influenced societies of the Hellenistic period (c. 323–31 BCE).
-
D.
event in ancient Rome
An event in ancient Rome is a specific occurrence or happening—such as a political assembly, religious festival, public spectacle, or military action—situated in Roman society and time that holds social, cultural, or historical significance.
-
E.
Byzantine history event
A Byzantine history event is a significant occurrence within the Eastern Roman (Byzantine) Empire that influenced its political, religious, military, social, or cultural development.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.