Triple
T22960857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cum sancta |
E570892
|
entity |
| Predicate | hasPapalReign |
P9032
|
FINISHED |
| Object | pontificate of Clement VIII |
—
|
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: pontificate of Clement VIII | Statement: [Cum sancta, hasPapalReign, pontificate of Clement VIII]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPapalReign Context triple: [Cum sancta, hasPapalReign, pontificate of Clement VIII]
-
A.
enthronedAsPope
Indicates that a person has been formally installed and recognized as the Pope.
-
B.
papacyOf
chosen
Indicates the relationship in which a specific papal office or tenure belongs to or is held by a particular pope.
-
C.
papacyDuringReignOf
Indicates that a papacy occurred during, and temporally overlapped with, the reign period of a specified ruler or authority.
-
D.
papalStatus
Indicates that an entity holds, held, or is assigned a particular status or role in relation to the papacy (e.g., pope, antipope, papal candidate, or related papal office).
-
E.
hasNotableReign
Indicates that an entity’s period of rule or governance is recognized as particularly significant or noteworthy.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f494348190a24f09d3495b0950 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:47 p.m.