Triple
T31420554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heiliges Kreuz |
E801517
|
entity |
| Predicate | centralInDoctrineOf |
P159778
|
FINISHED |
| Object | Soteriology |
—
|
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: Soteriology | Statement: [Heiliges Kreuz, centralInDoctrineOf, Soteriology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralInDoctrineOf Context triple: [Heiliges Kreuz, centralInDoctrineOf, Soteriology]
-
A.
primaryDoctrine
Indicates that the object represents the main or foundational doctrine associated with the subject.
-
B.
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.
-
C.
goalOfDoctrine
Indicates that a specified objective or end state is the intended goal or purpose of a particular doctrine.
-
D.
doctrinalDomain
chosen
Indicates the specific area of doctrine or body of teachings within which a belief, statement, or rule is classified.
-
E.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 30, 2026, 8:47 p.m.