Triple
T22399010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael I Rangabe |
E553708
|
entity |
| Predicate | enteredMonasticLife |
P40813
|
FINISHED |
| Object | after abdication |
—
|
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: after abdication | Statement: [Michael I Rangabe, enteredMonasticLife, after abdication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredMonasticLife Context triple: [Michael I Rangabe, enteredMonasticLife, after abdication]
-
A.
forcedIntoMonasticLifeBy
Indicates that one entity compelled another, against their will or under strong pressure, to enter and live a monastic or religious life.
-
B.
enteredConvent
Indicates that a person has joined and been admitted into a religious convent as a member.
-
C.
tookReligiousVowsOn
Indicates that an entity formally committed to religious vows on a specific date or occasion.
-
D.
tookReligiousVows
chosen
Indicates that an entity formally committed to a religious life by taking recognized vows within a religious tradition.
-
E.
monasticLife
Indicates a relationship where an entity lives according to monastic rules, practices, and commitments, typically within a religious community.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b28e58819090624f131ce63a9f |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:46 p.m.