Triple
T22791650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hincmar of Reims |
E564126
|
entity |
| Predicate | appointedArchbishopOfReims |
P3360
|
FINISHED |
| Object | 845 |
—
|
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: 845 | Statement: [Hincmar of Reims, appointedArchbishopOfReims, 845]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedArchbishopOfReims Context triple: [Hincmar of Reims, appointedArchbishopOfReims, 845]
-
A.
archbishopOf
chosen
Indicates that a person holds the ecclesiastical office of archbishop in relation to a specific diocese, region, or church jurisdiction.
-
B.
appointedArchbishopOfCanterburyIn
Indicates that a person was formally appointed to the position of Archbishop of Canterbury in a specified year or time period.
-
C.
archbishopricPredecessor
Indicates that one entity previously held the position of archbishop immediately before another entity in the same archbishopric office.
-
D.
appointedAsPrinceArchbishop
Indicates that an authority formally assigns a person to hold the office and role of Prince-Archbishop.
-
E.
formerArchbishop
Indicates that a person previously held the position or title of archbishop but no longer does.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cd5778c81909a18317ff98e341c |
completed | April 29, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:30 p.m.