Triple
T19205895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Area Bishop of Ripon |
E480230
|
entity |
| Predicate | predecessorTitleRelated |
P6041
|
FINISHED |
| Object | Bishop of Ripon |
—
|
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 of Ripon | Statement: [Area Bishop of Ripon, predecessorTitleRelated, Bishop of Ripon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorTitleRelated Context triple: [Area Bishop of Ripon, predecessorTitleRelated, Bishop of Ripon]
-
A.
predecessorTitleHolder
chosen
Indicates that one entity previously held a particular title or position before another entity.
-
B.
predecessorTitleContext
Indicates that the relationship specifies the contextual circumstances (such as role, period, or setting) under which a predecessor’s title is relevant or applies.
-
C.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
D.
successorTitlesComparedWith
Indicates that the titles of successor entities are being compared to determine their relative similarity, difference, or ordering.
-
E.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5f99cc39c81909499b8d0b78b4665 |
completed | April 20, 2026, 10:02 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:19 p.m.