Triple
T22301447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Vann |
E551266
|
entity |
| Predicate | installedAsBishopOfFortWorth |
P55939
|
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, installedAsBishopOfFortWorth, 2005-07-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installedAsBishopOfFortWorth Context triple: [Kevin Vann, installedAsBishopOfFortWorth, 2005-07-13]
-
A.
appointedBishopOf
Indicates that a person has been officially assigned or consecrated to serve as the bishop responsible for a particular diocese or ecclesiastical jurisdiction.
-
B.
consecratedAsBishopIn
chosen
Indicates that a person was formally ordained and installed as a bishop within a specified place, diocese, or jurisdiction.
-
C.
formerBishop
Indicates that a person once held the position of bishop but no longer occupies that office.
-
D.
appointedAsBishopOfLincoln
Indicates that a person was formally appointed to serve in the role of Bishop of Lincoln.
-
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_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.