Triple
T16296101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardinal-Priest of San Sisto |
E395650
|
entity |
| Predicate | appointedThrough |
P122568
|
FINISHED |
| Object | papal consistory |
—
|
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: papal consistory | Statement: [Cardinal-Priest of San Sisto, appointedThrough, papal consistory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedThrough Context triple: [Cardinal-Priest of San Sisto, appointedThrough, papal consistory]
-
A.
appointedWith
Indicates that one entity has been formally assigned or designated to a role, position, or responsibility in relation to another entity.
-
B.
appointedFrom
Indicates that an entity was selected or assigned to a position or role originating from a specified source, body, or prior position.
-
C.
appointedOver
Indicates that one entity has been formally assigned authority, responsibility, or a supervisory role over another entity.
-
D.
appointedAfter
Indicates that one entity was appointed to a position or role at a later time than another entity.
-
E.
appointedIn
Indicates that an entity is formally assigned or designated to a role, position, or office within a specific context, organization, or jurisdiction.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2dcdac819083918f0964dd5666 |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.