Triple
T33888042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iconoclast controversy |
E868682
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Byzantine historical event |
C34586
|
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: Byzantine historical event Context triple: [Iconoclast controversy, instanceOf, Byzantine historical event]
-
A.
Byzantine history event
chosen
A Byzantine history event is a significant occurrence within the Eastern Roman (Byzantine) Empire that influenced its political, religious, military, social, or cultural development.
-
B.
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.
-
C.
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.
-
D.
Byzantine institution
A Byzantine institution is a formal organization or structure within the Byzantine Empire—such as its imperial bureaucracy, church hierarchy, legal system, or military administration—defined by complex procedures, centralized authority, and a fusion of Roman, Christian, and local traditions.
-
E.
episode in Roman military history
An episode in Roman military history is a distinct event or campaign involving Roman armed forces that illustrates their strategies, conflicts, and impact on the expansion, defense, or transformation of Roman power.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:48 a.m.