Triple
T20379186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardinal-Priest of Santa Maria in Via |
E497774
|
entity |
| Predicate | cardinalRank |
P5046
|
FINISHED |
| Object | Cardinal-Priest |
—
|
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: Cardinal-Priest | Statement: [Cardinal-Priest of Santa Maria in Via, cardinalRank, Cardinal-Priest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardinalRank Context triple: [Cardinal-Priest of Santa Maria in Via, cardinalRank, Cardinal-Priest]
-
A.
rankInCollegeOfCardinals
Indicates the specific hierarchical position a cardinal holds within the College of Cardinals.
-
B.
cardinalName
Indicates that an entity has a specific cardinal (numerical order) name or label.
-
C.
rankInPapalOrders
Indicates the relative hierarchical position or level an entity holds within the structure of papal orders.
-
D.
rankInRomanCatholicChurch
Indicates that one entity holds a specific hierarchical or clerical position within the structure of the Roman Catholic Church in relation to another entity.
-
E.
ecclesiasticalRank
chosen
Indicates the hierarchical religious office or clerical status that one entity holds within a church or ecclesiastical organization.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678af651c8190b4922294a937e699 |
completed | April 20, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:27 a.m.