Triple
T30751482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Baptist Churches USA |
E782966
|
entity |
| Predicate | creedalStance |
P53021
|
FINISHED |
| Object | non-creedal |
—
|
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-creedal | Statement: [American Baptist Churches USA, creedalStance, non-creedal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creedalStance Context triple: [American Baptist Churches USA, creedalStance, non-creedal]
-
A.
positionOnCreed
Indicates a person's stance, alignment, or viewpoint regarding a particular creed, doctrine, or set of beliefs.
-
B.
doctrinalStance
Indicates the specific set of doctrines, beliefs, or official teachings that an entity adheres to or promotes.
-
C.
supportedCreed
Indicates that one entity endorsed, upheld, or actively promoted a particular belief system, doctrine, or set of principles associated with another entity.
-
D.
nonCreedal
chosen
Indicates that a religious group, belief system, or practice does not adhere to or require formal creeds or fixed doctrinal statements.
-
E.
creed
Indicates that an entity holds or is associated with a particular system of religious or ideological belief.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f91f0cc8190936582859f7d1683 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.