Triple
T17414867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainald of Dassel |
E423462
|
entity |
| Predicate | appointedAsImperialChancellor |
P325
|
FINISHED |
| Object | 1156 |
—
|
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: 1156 | Statement: [Rainald of Dassel, appointedAsImperialChancellor, 1156]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsImperialChancellor Context triple: [Rainald of Dassel, appointedAsImperialChancellor, 1156]
-
A.
precededInOfficeAsChancellorBy
Indicates that one individual assumed the role of Chancellor after another specific individual, who held the office immediately before them.
-
B.
namedForEmperor
Indicates that something (such as a place, object, or institution) is named in honor of a specific emperor.
-
C.
hasChancellor
chosen
Indicates that an entity holds the position or role of chancellor for another entity.
-
D.
formedUnderEmperor
Indicates that an entity (such as a group, institution, or administrative unit) was created or established during the reign or authority of a specific emperor.
-
E.
successorAsGermanEmperor
Indicates that one entity became the next holder of the title of German Emperor directly after another entity.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44231e29881909695a33aab1d49a2 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.