Triple
T31325187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian conquest of Phocaea |
E798863
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 6th-century BC event |
C34893
|
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: 6th-century BC event Context triple: [Persian conquest of Phocaea, instanceOf, 6th-century BC event]
-
A.
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.
-
B.
1st-century BCE conflict
A 1st-century BCE conflict is a historically documented military or political struggle that occurred between 100 BCE and 1 BCE, involving organized groups or states engaged in warfare or sustained hostilities.
-
C.
3rd-century event
A 3rd-century event is any significant historical occurrence that took place between the years 201 and 300 CE, encompassing political, social, cultural, military, or religious developments of that period.
-
D.
8th-century historical event
An 8th-century historical event is a significant occurrence between 700 and 799 CE that influenced the political, social, cultural, or religious development of societies during that period.
-
E.
6th-century conflict
chosen
A 6th-century conflict is a historically documented war, battle, or prolonged military-political struggle that occurred between 500 and 599 CE, involving organized groups or states and significantly impacting the societies of that era.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:15 p.m.