Triple
T11211418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdiocese of Toledo |
E265317
|
entity |
| Predicate | elevatedToPrimatialSee |
P97868
|
FINISHED |
| Object | 1088 |
—
|
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: 1088 | Statement: [Archdiocese of Toledo, elevatedToPrimatialSee, 1088]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToPrimatialSee Context triple: [Archdiocese of Toledo, elevatedToPrimatialSee, 1088]
-
A.
elevatedToPatriarchate
Indicates that an ecclesiastical jurisdiction or office was raised in rank or status to that of a patriarchate.
-
B.
primatialSee
Indicates that one primate (typically a senior bishop or primate) holds ecclesiastical oversight or jurisdiction over another see or church territory.
-
C.
ascendedTo
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location of another entity.
-
D.
elevatedToPrincipalityBy
Indicates that an entity was raised in status or rank to a principality by another entity or authority.
-
E.
elevatedToArcheparchy
Indicates that a church jurisdiction or eparchy has been raised in rank or status to that of an archeparchy.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d6f5d4819086dcb776a0d469e8 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.