Triple
T31418368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purgatory |
E801461
|
entity |
| Predicate | doctrineFormulatedIn |
P171849
|
FINISHED |
| Object | Latin Church |
—
|
NE NERFINISHED |
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: Latin Church | Statement: [Purgatory, doctrineFormulatedIn, Latin Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineFormulatedIn Context triple: [Purgatory, doctrineFormulatedIn, Latin Church]
-
A.
doctrineOf
Indicates a relationship where one entity is the doctrinal teaching, principle, or belief system associated with, derived from, or formally held by another entity.
-
B.
doctrineDiscussed
Indicates that a particular doctrine is the topic of discussion or analysis in a given context or interaction.
-
C.
doctrineRefined
Indicates that an existing doctrine has been further developed, clarified, or improved in its formulation or application.
-
D.
doctrineExplainedBy
Indicates that an explanation or interpretation is provided for a particular doctrine by a specified source or agent.
-
E.
codifiedDoctrine
Indicates that a set of beliefs, principles, or rules has been formally systematized and recorded as an official doctrine.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a5f656ec81909e02b0b873303adf |
completed | May 3, 2026, 1:33 a.m. |
Created at: April 30, 2026, 8:45 p.m.