Triple
T19931429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Area Bishop of Bradford |
E479062
|
entity |
| Predicate | establishedAsAreaBishopricIn |
P137885
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Area Bishop of Bradford, establishedAsAreaBishopricIn, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsAreaBishopricIn Context triple: [Area Bishop of Bradford, establishedAsAreaBishopricIn, 2014]
-
A.
establishedAsPrinceBishopric
Indicates that an entity was formally created or designated as a prince-bishopric, combining both secular princely authority and ecclesiastical bishopric status.
-
B.
bishopricEstablishedBefore
Indicates that the establishment of one bishopric occurred earlier in time than the establishment of another bishopric.
-
C.
wasPrinceBishopricUntil
Indicates that an entity functioned as a prince-bishopric up to (and including, or until) a specified point in time.
-
D.
establishedAsDiocese
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
E.
dioceseEstablishedBy
Indicates that a diocese was founded, created, or formally instituted by a particular person or authority.
- F. None of above. chosen
Provenance (4 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a13ebc08190a583aa4c5e9f6648 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.