Triple
T22301453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Vann |
E551266
|
entity |
| Predicate | consecrationDateAsBishop |
P3356
|
FINISHED |
| Object | 2005-07-13 |
—
|
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: 2005-07-13 | Statement: [Kevin Vann, consecrationDateAsBishop, 2005-07-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consecrationDateAsBishop Context triple: [Kevin Vann, consecrationDateAsBishop, 2005-07-13]
-
A.
consecratedAsBishopIn
Indicates that a person was formally ordained and installed as a bishop within a specified place, diocese, or jurisdiction.
-
B.
consecrationYearOfCurrentBishop
Indicates the year in which the current bishop associated with an entity was consecrated.
-
C.
consecratedBishopOn
Indicates that one entity performed the act of consecrating another entity as a bishop on a specific date or occasion.
-
D.
dateOfFirstBishopConsecration
Indicates the calendar date on which the first bishop associated with an entity was consecrated.
-
E.
consecrationDate
chosen
Indicates the date on which something (typically a building, object, or person) was formally dedicated or made sacred through a religious or ceremonial act.
- 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_69e11e46c0188190800181a4233f28fe |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157245ee481909a7a3397de3ae355 |
completed | April 29, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69e72ffa438481908f80879aef2a589b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:41 p.m.