Triple
T22791651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hincmar of Reims |
E564126
|
entity |
| Predicate | servedAsArchbishopOfReimsUntil |
P79267
|
FINISHED |
| Object | 882 |
—
|
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: 882 | Statement: [Hincmar of Reims, servedAsArchbishopOfReimsUntil, 882]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsArchbishopOfReimsUntil Context triple: [Hincmar of Reims, servedAsArchbishopOfReimsUntil, 882]
-
A.
endTimeAsArchbishopOfReims
chosen
Indicates the date and time when an individual’s tenure or service as Archbishop of Reims came to an end.
-
B.
servedAsArchbishopOfYorkUntil
Indicates having held the position of Archbishop of York up to a specified end date or point in time.
-
C.
startTimeAsArchbishopOfReims
Indicates the date and time when an individual began their tenure serving as Archbishop of Reims.
-
D.
enthronedAsMajorArchbishopOn
Indicates that someone was formally installed in office with the rank and authority of a Major Archbishop on a specific date or occasion.
-
E.
electedAsArchbishopOn
Indicates that an entity was chosen and formally appointed to the position of archbishop on a specific date.
- 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.