Triple
T3216918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishop of Cologne |
E67419
|
entity |
| Predicate | heldOfficeAs |
P30303
|
FINISHED |
| Object | territorial ruler |
—
|
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: territorial ruler | Statement: [Archbishop of Cologne, heldOfficeAs, territorial ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldOfficeAs Context triple: [Archbishop of Cologne, heldOfficeAs, territorial ruler]
-
A.
servedAs
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
-
B.
succeededInOffice
Indicates that one officeholder directly followed another in holding the same official position.
-
C.
heldJudicialPositionIn
Indicates that an entity served in an official judicial role or office within a specified jurisdiction or court.
-
D.
hasHeldOfficeType
chosen
Indicates that an entity has at some time occupied or served in a specified type or category of office or position.
-
E.
officeHolderServedUnder
Indicates that a person holding an office served in that role under the authority, administration, or leadership of another specified office holder or leader.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab0ae494819093d39c367facde27 |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.