Triple
T842090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Churches of Christ |
E18198
|
entity |
| Predicate | positionOnCreeds |
P15140
|
FINISHED |
| Object | no creed but the Bible |
—
|
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: no creed but the Bible | Statement: [Churches of Christ, positionOnCreeds, no creed but the Bible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnCreeds Context triple: [Churches of Christ, positionOnCreeds, no creed but the Bible]
-
A.
viewOnCreeds
chosen
Indicates a relationship where one party holds or expresses a particular stance, opinion, or interpretation regarding a set of creeds or formal beliefs.
-
B.
positionOnTheology
Indicates a stance, viewpoint, or opinion that one entity holds regarding theological beliefs, doctrines, or issues.
-
C.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
D.
relationToOtherCreeds
Indicates how one belief system, doctrine, or creed is positioned or related in comparison to other creeds.
-
E.
positionOnReason
Indicates that one entity holds a particular stance, justification, or rationale concerning another entity or issue.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abe6f0dc8190a1bebb5e21f4ceac |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7dfc5c8190890c9df485d73a86 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.