Triple
T9304588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishopric of Worms |
E223849
|
entity |
| Predicate | bishopricEstablishedBefore |
P87973
|
FINISHED |
| Object | 10th century |
—
|
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: 10th century | Statement: [Prince-Bishopric of Worms, bishopricEstablishedBefore, 10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bishopricEstablishedBefore Context triple: [Prince-Bishopric of Worms, bishopricEstablishedBefore, 10th century]
-
A.
isHistoricDioceseBishop
Indicates that a person holds or held the office of bishop in a diocese recognized as historic.
-
B.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
-
C.
dateOfFirstBishopConsecration
Indicates the calendar date on which the first bishop associated with an entity was consecrated.
-
D.
archbishopOf
Indicates that a person holds the ecclesiastical office of archbishop in relation to a specific diocese, region, or church jurisdiction.
-
E.
currentArchbishopStartYear
Indicates the calendar year in which the current archbishop began serving in that role.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1da623ac81908bab6dfb1bbce25d |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:36 p.m.