Triple
T3597511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Tyre |
E76174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in ancient history |
C13438
|
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 ancient history Context triple: [Siege of Tyre, instanceOf, event in ancient history]
-
A.
ancient civilization
An ancient civilization is a complex, organized society from antiquity characterized by urban development, social stratification, specialized labor, centralized governance, and enduring cultural, technological, and architectural achievements.
-
B.
event in church history
An event in church history is a significant occurrence or development within the life of the Christian church that influences its doctrine, practice, structure, or relationship with society over time.
-
C.
mythological event
A mythological event is a significant occurrence within a culture’s traditional stories or legends, often involving gods, heroes, or supernatural forces that explain natural phenomena, origins, or moral truths.
-
D.
5th-century event
A 5th-century event is a historically significant occurrence that took place between the years 401 and 500 CE, shaping the political, social, cultural, or religious landscape of its time.
-
E.
event in Myanmar history
An event in Myanmar history is a significant occurrence or development within Myanmar’s past that has shaped its political, social, cultural, or economic trajectory.
- F. None of above. chosen
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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:22 p.m.