Triple
T376614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostle Paul |
E8385
|
entity |
| Predicate | taughtDoctrine |
P1476
|
FINISHED |
| Object | justification by faith in Christ |
—
|
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: justification by faith in Christ | Statement: [Apostle Paul, taughtDoctrine, justification by faith in Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taughtDoctrine Context triple: [Apostle Paul, taughtDoctrine, justification by faith in Christ]
-
A.
teachesDoctrine
chosen
Indicates that one entity imparts, explains, or promotes a specific doctrine or set of beliefs to another entity.
-
B.
keyDoctrine
Indicates that something is a central or foundational doctrine within a belief system, organization, or theoretical framework.
-
C.
taughtAs
Indicates that one entity served as a teacher or instructor for another entity in an educational or training context.
-
D.
deniesDoctrine
Indicates that one entity rejects, opposes, or refuses to accept the truth or validity of a particular doctrine associated with another entity.
-
E.
doctrinalStatus
Indicates the formal standing or classification of a belief, teaching, or doctrine within a particular religious or ideological system.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec169a848190a577aa093c878839 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96351cc8190a55adf95f8c27e9e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.