Triple
T17414866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainald of Dassel |
E423462
|
entity |
| Predicate | appointedAsArchbishopOfCologne |
P92918
|
FINISHED |
| Object | 1159 |
—
|
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: 1159 | Statement: [Rainald of Dassel, appointedAsArchbishopOfCologne, 1159]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsArchbishopOfCologne Context triple: [Rainald of Dassel, appointedAsArchbishopOfCologne, 1159]
-
A.
appointedAsArchbishopOfYork
Indicates that a person has been formally appointed to serve in the role of Archbishop of York.
-
B.
appointedAsArchbishop
chosen
Indicates that an authority formally assigned a person to hold the office or role of an archbishop.
-
C.
startTimeAsArchbishopOfCologne
Indicates the date and time when an individual began serving in the role of Archbishop of Cologne.
-
D.
electedAsArchbishopOn
Indicates that an entity was chosen and formally appointed to the position of archbishop on a specific date.
-
E.
enthronedAsMajorArchbishopOn
Indicates that someone was formally installed in office with the rank and authority of a Major Archbishop on a specific date or occasion.
- 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.