Triple
T1949602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Baptist Convention |
E42128
|
entity |
| Predicate | membershipUnit |
P33432
|
FINISHED |
| Object | member churches |
—
|
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: member churches | Statement: [Southern Baptist Convention, membershipUnit, member churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membershipUnit Context triple: [Southern Baptist Convention, membershipUnit, member churches]
-
A.
membershipStructure
Indicates the organizational or hierarchical arrangement that defines how members are grouped, related, and governed within a collective or system.
-
B.
membershipBased
Indicates that access, participation, or inclusion in something is conditional on holding a membership or belonging to a defined group.
-
C.
membershipIn
Indicates that an entity belongs to, is part of, or holds membership in a particular group, organization, or collection.
-
D.
clubMembership
Indicates that an entity belongs to, is enrolled in, or holds membership status within a particular club.
-
E.
memberCategory
Indicates that an entity belongs to or is classified under a specific category or group.
- 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.