Triple
T519278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good News Bible |
E10776
|
entity |
| Predicate | doctrineStance |
P5485
|
FINISHED |
| Object | non-denominational |
—
|
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: non-denominational | Statement: [Good News Bible, doctrineStance, non-denominational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineStance Context triple: [Good News Bible, doctrineStance, non-denominational]
-
A.
stateDoctrine
Indicates that a state or government officially endorses, promotes, or is guided by a particular doctrine, ideology, or set of principles.
-
B.
concernsDoctrine
chosen
Indicates that something is related or pertains specifically to a particular doctrine or set of doctrinal principles.
-
C.
deniesDoctrine
Indicates that one entity rejects, opposes, or refuses to accept the truth or validity of a particular doctrine associated with another entity.
-
D.
doctrineSourceFor
Indicates that one entity serves as the originating basis or authoritative source of doctrine, teachings, or principles for another entity.
-
E.
confirmedDoctrine
Indicates that an authority has officially validated, endorsed, or ratified a particular doctrine as true or acceptable.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f19ee6748190916603ef3a9e27f3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f016ba5c81909825b04e7525b4ab |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.