Triple
T14197887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boniface Wimmer |
E351886
|
entity |
| Predicate | ordainedAsPriestIn |
P14734
|
FINISHED |
| Object | 1831 |
—
|
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: 1831 | Statement: [Boniface Wimmer, ordainedAsPriestIn, 1831]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordainedAsPriestIn Context triple: [Boniface Wimmer, ordainedAsPriestIn, 1831]
-
A.
ordainedIn
Indicates that an individual was formally appointed or consecrated to a religious office or role at a specific place or within a particular institution.
-
B.
wasOrdainedAs
chosen
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
-
C.
ordainedBy
Indicates that an entity has been formally appointed, consecrated, or invested with authority by another entity.
-
D.
consecratedAsBishopIn
Indicates that a person was formally ordained and installed as a bishop within a specified place, diocese, or jurisdiction.
-
E.
ordainedLaterKnownAs
Indicates that an entity was ordained under one name or identity and later became known by a different name or identity.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61e30f208190b61c1c7bd3501156 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:04 a.m.