Triple
T9751157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ignatius Aphrem II |
E236441
|
entity |
| Predicate | enthroned |
P25237
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Ignatius Aphrem II, enthroned, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enthroned Context triple: [Ignatius Aphrem II, enthroned, 2014]
-
A.
throne
Indicates that an entity holds or occupies a position of sovereign authority or rulership, typically as a monarch.
-
B.
acceptedThrone
chosen
Indicates that an entity has agreed to assume and take on the role and authority associated with a throne or rulership.
-
C.
invitedToThrone
Indicates that one entity has been formally asked or summoned to be present at, or potentially take a role in, a throne or royal seat of power.
-
D.
lostThroneTo
Indicates that one entity was previously in possession of a throne or rulership but was defeated or displaced so that another entity took that throne instead.
-
E.
tookThroneFollowing
Indicates that one entity assumed or claimed a throne or rulership position directly after another entity, in a succession context.
- 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_69ca84d4eddc8190996fec1417d2bae8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f6bb4088190ab8d52ef61d24bee |
completed | April 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:24 p.m.