Triple
T19920730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markus Sittikus von Hohenems |
E478786
|
entity |
| Predicate | heldEcclesiasticalRank |
P5046
|
FINISHED |
| Object | Archbishop |
—
|
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: Archbishop | Statement: [Markus Sittikus von Hohenems, heldEcclesiasticalRank, Archbishop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldEcclesiasticalRank Context triple: [Markus Sittikus von Hohenems, heldEcclesiasticalRank, Archbishop]
-
A.
heldEcclesiasticalAuthorityIn
Indicates that an entity possessed official religious or church authority within a specified place or jurisdiction.
-
B.
ecclesiasticalRank
chosen
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
-
C.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
D.
hasDiocesanRank
Indicates that an entity holds a specific hierarchical rank or status within a diocese.
-
E.
ecclesiasticalRole
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659c564788190a3893fc73fc4922b |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.