Triple
T14914536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synod of Constantinople in 843 |
E371347
|
entity |
| Predicate | historicalPeriodEnded |
P76220
|
FINISHED |
| Object | second Iconoclast period |
—
|
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: second Iconoclast period | Statement: [Synod of Constantinople in 843, historicalPeriodEnded, second Iconoclast period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodEnded Context triple: [Synod of Constantinople in 843, historicalPeriodEnded, second Iconoclast period]
-
A.
endedEra
Indicates that one entity brought about or marked the conclusion of a particular era associated with another entity.
-
B.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
C.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
D.
chronologyEnd
chosen
Indicates that one event, state, or time interval marks the ending point or conclusion of another in a temporal sequence.
-
E.
colonialPeriodEnd
Indicates the time or event at which a colonial period or colonial rule over a territory comes to an end.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded61f1d488190995f847f84d72cdc |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:27 a.m.