Triple
T30210555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icons of the Theotokos |
E768054
|
entity |
| Predicate | opposedDuring |
P181334
|
FINISHED |
| Object | Byzantine Iconoclasm |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Byzantine Iconoclasm | Statement: [Icons of the Theotokos, opposedDuring, Byzantine Iconoclasm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedDuring Context triple: [Icons of the Theotokos, opposedDuring, Byzantine Iconoclasm]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposedConference
Indicates that one entity actively resists, counters, or works against another entity within the context of a conference or formal gathering.
-
C.
opposedShow
Indicates that one show is in opposition or contrast to another show, such as competing with or countering it.
-
D.
opposedControlBy
Indicates that one entity resists, challenges, or acts against the control or authority exerted by another entity.
-
E.
opposedOutcome
Indicates that one entity’s outcome is in conflict with, counters, or works against the outcome associated with another entity.
- F. None of above. chosen
Provenance (4 batches)
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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_69f7688cea58819098bdfd7c80df7634 |
completed | May 3, 2026, 3:23 p.m. |
Created at: April 29, 2026, 7:32 p.m.