Triple
T34416819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrine ministry |
E883420
|
entity |
| Predicate | continuedInOfficeOf |
P52384
|
FINISHED |
| Object | pope |
—
|
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: pope | Statement: [Petrine ministry, continuedInOfficeOf, pope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedInOfficeOf Context triple: [Petrine ministry, continuedInOfficeOf, pope]
-
A.
representsInOffice
Indicates that one entity serves as an official representative of another entity within a specific office, position, or institutional role.
-
B.
followsInOffice
Indicates that one officeholder directly succeeds another in holding the same office or position.
-
C.
allowsContinuationOfOffice
chosen
Indicates that one entity grants or enables another entity to continue holding or exercising a particular office or position beyond its current term or conditions.
-
D.
officeContinuedBy
Indicates that one office or term in a position is directly succeeded or carried on by another office or term.
-
E.
aboutOfficeHeld
Indicates that one entity is related to, or provides information about, a specific office or position that is or was held by another entity.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 1, 2026, 1:59 a.m.