Triple
T13465167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Hieria |
E311476
|
entity |
| Predicate | positionOnIcons |
P93820
|
FINISHED |
| Object | iconoclastic |
—
|
LITERAL FINISHED |
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: iconoclastic | Statement: [Council of Hieria, positionOnIcons, iconoclastic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnIcons Context triple: [Council of Hieria, positionOnIcons, iconoclastic]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
iconographicPosition
Indicates the relative placement or arrangement of elements within an image or visual composition, specifying where something appears in the iconographic layout.
-
C.
positionOnIdentity
Indicates a stance, view, or opinion that an entity holds regarding identity-related issues or characteristics.
-
D.
stanceOnIcons
chosen
Indicates a subject’s position, attitude, or viewpoint regarding the use, value, or treatment of icons.
-
E.
positionOfEmblem
Indicates the spatial placement or location of an emblem relative to a reference object or surface.
- F. None of above.
Provenance (3 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0f1830819085700b4521e44678 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:41 p.m.