Triple
T2851755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William White |
E63106
|
entity |
| Predicate | consecratedAs |
P21434
|
FINISHED |
| Object | bishop |
—
|
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: bishop | Statement: [William White, consecratedAs, bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consecratedAs Context triple: [William White, consecratedAs, bishop]
-
A.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
B.
consecrated
chosen
Indicates that an entity has been formally dedicated or made sacred for a religious or holy purpose.
-
C.
presanctifiedGiftsConsecratedAt
Indicates that the presanctified gifts were consecrated at a particular time, place, or liturgical celebration.
-
D.
consecrationDate
Indicates the date on which something (typically a building, object, or person) was formally dedicated or made sacred through a religious or ceremonial act.
-
E.
canonizedAs
Indicates that an authority, typically a religious institution, has formally declared someone to be a saint or holy figure.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf5ca2648190bd32c6ec4b0dd3b6 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.