Triple
T17853531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toribio Alfonso de Mogrovejo |
E445870
|
entity |
| Predicate | enteredLimaAsArchbishop |
P60392
|
FINISHED |
| Object | 1581 |
—
|
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: 1581 | Statement: [Toribio Alfonso de Mogrovejo, enteredLimaAsArchbishop, 1581]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredLimaAsArchbishop Context triple: [Toribio Alfonso de Mogrovejo, enteredLimaAsArchbishop, 1581]
-
A.
startTimeAsArchbishopOfLima
chosen
Indicates the date and time when an individual began serving in the role of Archbishop of Lima.
-
B.
successorAsArchbishopOfLima
Indicates that one individual became the next Archbishop of Lima following another individual in that ecclesiastical office.
-
C.
endTimeAsArchbishopOfLima
Indicates the date and time when an individual's tenure as Archbishop of Lima concluded.
-
D.
predecessorAsArchbishopOfLima
Indicates that one entity previously held the position of Archbishop of Lima immediately before the other entity.
-
E.
appointedAsArchbishop
Indicates that an authority formally assigned a person to hold the office or role of an archbishop.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49001d8b881908c8d4efc3d7ff04f |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.