Triple
T461005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Protestant churches |
E7335
|
entity |
| Predicate | hasKeyInstitutionType |
P15066
|
FINISHED |
| Object | local congregation |
—
|
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: local congregation | Statement: [Black Protestant churches, hasKeyInstitutionType, local congregation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyInstitutionType Context triple: [Black Protestant churches, hasKeyInstitutionType, local congregation]
-
A.
hasKeyAgency
Indicates that an entity serves as the primary responsible or controlling agency for another entity, action, or process.
-
B.
hasStateInstitution
Indicates that a particular state possesses, governs, or is served by a specific institution operating under its authority or within its jurisdiction.
-
C.
hasAffiliationType
Indicates that one entity is connected to another through a specified kind or category of affiliation or association.
-
D.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
-
E.
hasKeyOrganization
Indicates that an entity is associated with or primarily represented by a main or primary organization.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efbed5b88190a45716812eb4cfdf |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2ede75b6c81908350103d21f22a03 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef257a548190a96bfa0cf6183976 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.