Triple
T1949614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Baptist Convention |
E42128
|
entity |
| Predicate | positionOnLGBTClergy |
P33434
|
FINISHED |
| Object | does not affirm LGBT clergy |
—
|
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: does not affirm LGBT clergy | Statement: [Southern Baptist Convention, positionOnLGBTClergy, does not affirm LGBT clergy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnLGBTClergy Context triple: [Southern Baptist Convention, positionOnLGBTClergy, does not affirm LGBT clergy]
-
A.
clergyCan
Indicates that members of the clergy are permitted or authorized to perform a specified action or exercise a particular role or function.
-
B.
hasClergy
Indicates that an organization or institution possesses or is served by members of the clergy.
-
C.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
D.
workedAsClergymanIn
Indicates that a person served in a religious or clerical role within a specified place or institution.
-
E.
clergyPractice
Indicates that a member of the clergy engages in, performs, or follows a particular religious practice or ritual.
- F. None of above. chosen
Provenance (4 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_69a8870e08fc8190a319cbf2600db15f |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb332b014819085bfc88d66cfc10a |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb1ddccbc8190bf2bd8bac673c0c5 |
completed | March 7, 2026, 5:04 a.m. |
Created at: March 4, 2026, 7:36 p.m.