Triple
T3396082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander, Bishop of Lincoln |
E71531
|
entity |
| Predicate | appointedAsBishopOfLincoln |
P49403
|
FINISHED |
| Object | 1123 |
—
|
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: 1123 | Statement: [Alexander, Bishop of Lincoln, appointedAsBishopOfLincoln, 1123]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsBishopOfLincoln Context triple: [Alexander, Bishop of Lincoln, appointedAsBishopOfLincoln, 1123]
-
A.
appointedBishopOfWinchester
Indicates that a person was formally appointed to serve as the Bishop of Winchester.
-
B.
appointedAsArchbishopOfNewYorkOn
Indicates that a person was formally appointed to the position of Archbishop of New York on a specific date.
-
C.
electedAsPresidingBishopOn
Indicates that an individual was chosen and formally appointed to serve as Presiding Bishop on a specific date.
-
D.
startTimeAsArchbishopOfCanterbury
Indicates the date and time when an individual began serving as Archbishop of Canterbury.
-
E.
archbishopOf
Indicates that a person holds the ecclesiastical office of archbishop in relation to a specific diocese, region, or church jurisdiction.
- F. None of above. chosen
Provenance (4 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb856158c81908dd7d3f1f8d6af74 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb2e426b88190b82d9830149b142e |
completed | March 8, 2026, 5:33 p.m. |
Created at: March 8, 2026, 3:14 p.m.