Triple
T30137986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregory XIV |
E766048
|
entity |
| Predicate | appointedBishopOfCremona |
P67420
|
FINISHED |
| Object | 1560 |
—
|
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: 1560 | Statement: [Gregory XIV, appointedBishopOfCremona, 1560]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedBishopOfCremona Context triple: [Gregory XIV, appointedBishopOfCremona, 1560]
-
A.
appointedBishopOf
chosen
Indicates that a person has been officially assigned or consecrated to serve as the bishop responsible for a particular diocese or ecclesiastical jurisdiction.
-
B.
bishopAppointed
Indicates that an individual has been formally appointed to the position or office of bishop by an authorized authority.
-
C.
appointedBishopBy
Indicates that one entity was formally made a bishop through the authority or decision of another entity.
-
D.
appointedArchbishopOfFlorenceOn
Indicates that a person was formally appointed to the position of Archbishop of Florence on a specific date.
-
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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 7:16 p.m.