Triple
T15684251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefan Nemanja |
E380154
|
entity |
| Predicate | roleAfterAbdication |
P92702
|
FINISHED |
| Object | monk |
—
|
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: monk | Statement: [Stefan Nemanja, roleAfterAbdication, monk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAfterAbdication Context triple: [Stefan Nemanja, roleAfterAbdication, monk]
-
A.
afterAbdication
Indicates that one event, state, or action occurs subsequent to the abdication of a person from a position of authority or office.
-
B.
politicalStatusAfterAbdication
chosen
Indicates the political role, position, or status an individual holds after formally abdicating a previous office or throne.
-
C.
successorOfficeOfCoSovereign
Indicates that one office is the subsequent or replacement office to a previous co-sovereign office in a line of succession.
-
D.
titleAfterAbdication
Indicates the formal title or designation a person holds after they have abdicated a previous position of authority or rank.
-
E.
monarchSuccessor
Indicates that one monarch directly follows another in a royal line of succession.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f31b5b881908e46ecd9fc6048ab |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8c856c8190882330114f9a1a5f |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:43 a.m.