Triple
T34554456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raymond of Toledo |
E887163
|
entity |
| Predicate | appointedAsArchbishopOfToledo |
P92918
|
FINISHED |
| Object | 1125 |
—
|
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: 1125 | Statement: [Raymond of Toledo, appointedAsArchbishopOfToledo, 1125]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsArchbishopOfToledo Context triple: [Raymond of Toledo, appointedAsArchbishopOfToledo, 1125]
-
A.
appointedAsArchbishop
chosen
Indicates that an authority formally assigned a person to hold the office or role of an archbishop.
-
B.
appointedAsPrinceArchbishop
Indicates that an authority formally assigns a person to hold the office and role of Prince-Archbishop.
-
C.
appointedArchbishopOfFlorenceOn
Indicates that a person was formally appointed to the position of Archbishop of Florence on a specific date.
-
D.
appointedAsArchbishopOfBostonBy
Indicates that one entity formally appointed another entity to the position of Archbishop of Boston.
-
E.
appointedBishopOf
Indicates that a person has been officially assigned or consecrated to serve as the bishop responsible for a particular diocese or ecclesiastical jurisdiction.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 1, 2026, 2:02 a.m.