Triple
T20381700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope Sylvester III |
E497847
|
entity |
| Predicate | papacyOutcome |
P139906
|
FINISHED |
| Object | papacy annulled |
—
|
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: papacy annulled | Statement: [Pope Sylvester III, papacyOutcome, papacy annulled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: papacyOutcome Context triple: [Pope Sylvester III, papacyOutcome, papacy annulled]
-
A.
papacyOf
Indicates the relationship in which a specific papal office or tenure belongs to or is held by a particular pope.
-
B.
papalElection
Indicates the process or event in which a new pope is chosen and formally elected to the papal office.
-
C.
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).
-
D.
electedPope
Indicates that one person or body has chosen or appointed another individual to serve as Pope.
-
E.
papacyDuringReignOf
Indicates that a papacy occurred during, and temporally overlapped with, the reign period of a specified ruler or authority.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678b0ee708190bdbe4aab28a61525 |
completed | April 20, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:27 a.m.