Triple
T35125881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope John III |
E1014300
|
entity |
| Predicate | hasNumberInPapalSequence |
P14899
|
FINISHED |
| Object | 61 |
—
|
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: 61 | Statement: [Pope John III, hasNumberInPapalSequence, 61]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberInPapalSequence Context triple: [Pope John III, hasNumberInPapalSequence, 61]
-
A.
hasPapalNameNumber
Indicates that a pope’s chosen papal name is associated with a specific ordinal number (e.g., John Paul II has papal name number 2).
-
B.
popeNumber
Indicates the ordinal position of a person in the historical sequence of popes (e.g., being the 5th, 23rd, or 266th pope).
-
C.
ordinalInPapalSuccession
chosen
Indicates the numerical position an individual holds in the chronological sequence of popes within the papal succession.
-
D.
documentNumberInPapacy
Indicates that a specific document is assigned a particular identifying number within the context of a given papacy.
-
E.
hasNextPope
Indicates that one pope is the immediate successor of another in the papal sequence.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: May 3, 2026, 4:02 p.m.