Triple
T20086987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Leiden |
E496160
|
entity |
| Predicate | typeOfJurisdictionHead |
P3734
|
FINISHED |
| Object | diocesan bishop |
—
|
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: diocesan bishop | Statement: [Bishop of Leiden, typeOfJurisdictionHead, diocesan bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfJurisdictionHead Context triple: [Bishop of Leiden, typeOfJurisdictionHead, diocesan bishop]
-
A.
typeOfJurisdictionBody
Indicates that one entity functions as the jurisdictional authority or governing body for the other entity.
-
B.
typeOfJurisdiction
chosen
Indicates the specific kind or category of legal authority or control that one jurisdiction holds in relation to a given legal or administrative context.
-
C.
typeOfJurisdictionRepresentation
Indicates the specific kind or category of jurisdictional authority that is being represented in a given context.
-
D.
judicialHead
Indicates that one entity serves as the chief or leading judicial authority over another entity, such as a court or legal body.
-
E.
typeOfJurisdictionCreated
Indicates that one entity establishes or defines the kind of legal or administrative jurisdiction associated with another entity.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655ba40c8190adea0e271a1249cf |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:12 p.m.