Triple
T28824647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Photinus of Sirmium |
E727867
|
entity |
| Predicate | deposedFrom |
P165637
|
FINISHED |
| Object | Bishopric of Sirmium |
—
|
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: Bishopric of Sirmium | Statement: [Photinus of Sirmium, deposedFrom, Bishopric of Sirmium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deposedFrom Context triple: [Photinus of Sirmium, deposedFrom, Bishopric of Sirmium]
-
A.
deposedBy
Indicates that an entity has been removed from a position of power or authority by another entity.
-
B.
wasDeposedAt
Indicates that an entity lost its position, power, or office through deposition at a specific time or event.
-
C.
deposedInContextOf
Indicates that an entity was removed from power or office specifically within, or as a consequence of, a particular event, situation, or broader contextual circumstance.
-
D.
deposes
Indicates the action by which one party forcibly removes another from a position of power or authority.
-
E.
deposedYear
Indicates the year in which an entity was removed from power or forced out of an official position.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:35 a.m.