Triple
T21168383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theological Commonplaces |
E521629
|
entity |
| Predicate | coversDoctrine |
P15801
|
FINISHED |
| Object | justification by faith |
—
|
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 | Statement: [Theological Commonplaces, coversDoctrine, justification by faith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversDoctrine Context triple: [Theological Commonplaces, coversDoctrine, justification by faith]
-
A.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
B.
extendsDoctrineTo
Indicates that a doctrine, principle, or rule is applied or carried over from one context, entity, or domain to another, broadening its scope or coverage.
-
C.
containsDoctrine
chosen
Indicates that one entity includes, embodies, or incorporates the doctrine, principles, or teachings represented by another entity.
-
D.
usesDoctrine
Indicates that one entity applies, follows, or relies on a particular doctrine in its actions or reasoning.
-
E.
concernsDoctrine
Indicates that something is related or pertains specifically to a particular doctrine or set of doctrinal 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72710c73881908d41aedff8984da9 |
completed | April 21, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3 p.m.