Triple
T11012905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Radevormwald |
E260286
|
entity |
| Predicate | hasRulingOffice |
P60156
|
FINISHED |
| Object | 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: bishop | Statement: [Bishopric of Radevormwald, hasRulingOffice, bishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulingOffice Context triple: [Bishopric of Radevormwald, hasRulingOffice, bishop]
-
A.
hasSupremeOffice
Indicates that an entity holds or occupies the highest-ranking official position within a given organization, institution, or jurisdiction.
-
B.
hadRulingSeat
Indicates that an entity held an official position of authority or judgment within a governing or decision-making body.
-
C.
hasOffice
Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
-
D.
governingOffice
chosen
Indicates the official position or office through which an entity exercises governing authority over a jurisdiction or organization.
-
E.
hasLocalGovernmentOffice
Indicates that a local government office is present or established within a specified location or jurisdiction.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7978b1e888190b297f107f6021b59 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.