Triple
T2431419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dexter Avenue King Memorial Baptist Church |
E52853
|
entity |
| Predicate | pastorStartDate |
P37586
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Dexter Avenue King Memorial Baptist Church, pastorStartDate, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pastorStartDate Context triple: [Dexter Avenue King Memorial Baptist Church, pastorStartDate, 1954]
-
A.
startOfPastorate
chosen
Indicates the point in time when a person begins serving in the role of pastor for a particular congregation or parish.
-
B.
isPrincipalPastorOf
Indicates that one entity serves or has served as the main or lead pastor of another entity, typically a church or religious organization.
-
C.
previousHolderStartDate
Indicates the date on which the immediately preceding holder of something (e.g., a position, title, or asset) began their tenure or ownership.
-
D.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
E.
beganTermAsPresidingBishopOn
Indicates the date on which an individual started their term serving in the role of Presiding Bishop.
- 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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcc74a5108190a3a9631b0cc1a127 |
completed | March 7, 2026, 6:57 a.m. |
| PD | Predicate disambiguation | batch_69abc5aa1b60819081b87f7985c6cff3 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:43 p.m.