Triple
T37865317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Wheeling–Charleston |
E944453
|
entity |
| Predicate | officeRenamedWith |
P199577
|
FINISHED |
| Object | expansion to Diocese of Wheeling–Charleston |
—
|
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: expansion to Diocese of Wheeling–Charleston | Statement: [Bishop of Wheeling–Charleston, officeRenamedWith, expansion to Diocese of Wheeling–Charleston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeRenamedWith Context triple: [Bishop of Wheeling–Charleston, officeRenamedWith, expansion to Diocese of Wheeling–Charleston]
-
A.
officeRenamedTo
chosen
Indicates that an office previously known by one name has been changed or renamed to a new specified name.
-
B.
officeRenamedIn
Indicates that an office changed its name in a specific time period or event.
-
C.
officeRenamedFrom
Indicates that an office currently known by one name previously had a different name.
-
D.
officeRenamedAsPremier
Indicates that an office or position has been renamed to the title "Premier."
-
E.
officeTransformedInto
Indicates that one office has been converted or changed into another office or a different type of space.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
Created at: May 3, 2026, 4:19 p.m.