Triple
T582410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Leo X |
E15085
|
entity |
| Predicate | createdCardinalInConsistory |
P14900
|
FINISHED |
| Object | 1489-03-23 |
—
|
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: 1489-03-23 | Statement: [Pope Leo X, createdCardinalInConsistory, 1489-03-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdCardinalInConsistory Context triple: [Pope Leo X, createdCardinalInConsistory, 1489-03-23]
-
A.
createdCardinalBy
Indicates that something was brought into existence or produced through the actions or authority of a cardinal.
-
B.
appointedCardinalBy
chosen
Indicates that one entity has formally elevated or designated another entity to the rank or office of cardinal.
-
C.
cardinalCreationDate
Indicates the specific date on which something was originally created or brought into existence.
-
D.
cardinalCreatedBy
Indicates that a cardinal (a high-ranking clergy member) was created or appointed by a specific authority or person.
-
E.
ordinalInPapalSuccession
Indicates the numerical position an individual holds in the chronological sequence of popes within the papal succession.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b85becc8190b4d98c00e5fa7c04 |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.