Triple
T7619293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Cross |
E172446
|
entity |
| Predicate | centralInDoctrine |
P4306
|
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: [Holy Cross, centralInDoctrine, soteriology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralInDoctrine Context triple: [Holy Cross, centralInDoctrine, soteriology]
-
A.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
keyDoctrine
chosen
Indicates that something is a central or foundational doctrine within a belief system, organization, or theoretical framework.
-
C.
confirmedDoctrine
Indicates that an authority has officially validated, endorsed, or ratified a particular doctrine as true or acceptable.
-
D.
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.
-
E.
stateDoctrine
Indicates that a state or government officially endorses, promotes, or is guided by a particular doctrine, ideology, or set of principles.
- 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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:55 p.m.