Triple
T3193154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishopric of Paderborn |
E66870
|
entity |
| Predicate | hadJudicialAuthority |
P808
|
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, hadJudicialAuthority, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadJudicialAuthority Context triple: [Prince-Bishopric of Paderborn, hadJudicialAuthority, yes]
-
A.
hadJudicialFunction
Indicates that an entity exercised or was assigned an official judicial role, authority, or responsibility in relation to another entity or context.
-
B.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
C.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
-
D.
hasJurisdictionOver
chosen
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
E.
hasLegalAuthorityFrom
Indicates that one entity possesses formal legal power, rights, or authorization that originates from or is granted by 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_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. |
Created at: March 8, 2026, 3:07 p.m.