Triple
T27553346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-bishop of Neuss |
E695564
|
entity |
| Predicate | combinedOffice |
P3897
|
FINISHED |
| Object | spiritual authority |
—
|
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: spiritual authority | Statement: [Prince-bishop of Neuss, combinedOffice, spiritual authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinedOffice Context triple: [Prince-bishop of Neuss, combinedOffice, spiritual authority]
-
A.
combinedOfficeName
Indicates that an entity’s office is identified by a name formed by combining multiple office-related designations into a single label.
-
B.
combinedWithOffice
chosen
Indicates that something is joined or integrated together with an office, typically forming a combined role, function, or arrangement.
-
C.
combinedOfficeExistedUntil
Indicates that a merged or joint office or position remained in existence up to a specified end time or date.
-
D.
includedOffice
Indicates that one office is contained within, or forms part of, another office or organizational unit.
-
E.
otherOffice
Indicates that one office is an alternative or additional office associated with the same organization, person, or entity as another office.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f8e4ab88190bfe86343b948a401 |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:35 p.m.