Triple
T25017413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladislaus II, King of Bohemia |
E626176
|
entity |
| Predicate | resignedThrone |
P15934
|
FINISHED |
| Object | 1172 |
—
|
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: 1172 | Statement: [Vladislaus II, King of Bohemia, resignedThrone, 1172]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resignedThrone Context triple: [Vladislaus II, King of Bohemia, resignedThrone, 1172]
-
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.
abdicatingMonarch
Indicates a relationship where a monarch formally renounces or relinquishes their throne and ruling authority.
-
C.
abdicatedFrom
chosen
Indicates that a person has formally renounced or given up a position of authority, office, or throne associated with a particular entity or domain.
-
D.
abdicatedInFavorOf
Indicates that one entity has voluntarily renounced a position, role, or right so that another specific entity may assume it.
-
E.
abdicatedDuring
Indicates that a ruler or officeholder gave up their position or authority during a specified event or time period.
- 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:06 a.m.