Triple
T21353058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich Wetter |
E526537
|
entity |
| Predicate | appointedBishopOfSpeyer |
P143959
|
FINISHED |
| Object | 1968-05-28 |
—
|
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: 1968-05-28 | Statement: [Friedrich Wetter, appointedBishopOfSpeyer, 1968-05-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedBishopOfSpeyer Context triple: [Friedrich Wetter, appointedBishopOfSpeyer, 1968-05-28]
-
A.
appointedBishopOfWinchester
Indicates that a person was formally appointed to serve as the Bishop of Winchester.
-
B.
appointedBishopOf
Indicates that a person has been officially assigned or consecrated to serve as the bishop responsible for a particular diocese or ecclesiastical jurisdiction.
-
C.
appointedAsPrinceArchbishop
Indicates that an authority formally assigns a person to hold the office and role of Prince-Archbishop.
-
D.
appointedAsBishopOfHildesheimBy
Indicates that an entity was appointed to the position of Bishop of Hildesheim by another specific entity.
-
E.
appointedBishopBy
Indicates that one entity was formally made a bishop through the authority or decision of another entity.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8ad34a1d48190b14fa099968faf7c |
completed | April 22, 2026, 11:12 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e61b3e47f881908fb2aac9bd2bfb58 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 16, 2026, 5:05 p.m.