Triple
T3193134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishopric of Paderborn |
E66870
|
entity |
| Predicate | hadSecularAuthority |
P46562
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Prince-Bishopric of Paderborn, hadSecularAuthority, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSecularAuthority Context triple: [Prince-Bishopric of Paderborn, hadSecularAuthority, yes]
-
A.
heldEcclesiasticalAuthorityIn
Indicates that an entity possessed official religious or church authority within a specified place or jurisdiction.
-
B.
hasSecularAspects
Indicates that something includes or exhibits non-religious, worldly, or secular characteristics or dimensions.
-
C.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
D.
hasSecularUse
Indicates that something is used in a non-religious, worldly, or secular context or purpose.
-
E.
hadNationalChurch
Indicates that a country or region recognized a particular church as its official or primary national religious institution.
- 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_69ad8588ba18819086a10951c32ecb80 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada713bf0c81908f3143f45f63a5ad |
completed | March 8, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:07 p.m.