Triple
T18360417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franciscus Sonnius |
E439898
|
entity |
| Predicate | appointedAsBishopOfHertogenbosch |
P67420
|
FINISHED |
| Object | 1570 |
—
|
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: 1570 | Statement: [Franciscus Sonnius, appointedAsBishopOfHertogenbosch, 1570]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsBishopOfHertogenbosch Context triple: [Franciscus Sonnius, appointedAsBishopOfHertogenbosch, 1570]
-
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.
appointedAsBishopOfHildesheimBy
Indicates that an entity was appointed to the position of Bishop of Hildesheim by another specific entity.
-
C.
consecratedAsBishopIn
Indicates that a person was formally ordained and installed as a bishop within a specified place, diocese, or jurisdiction.
-
D.
appointedBishopOfWinchester
Indicates that a person was formally appointed to serve as the Bishop of Winchester.
-
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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516db045c8190b20c209225a53b9a |
completed | April 19, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.