Triple
T3575359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebenezer Baptist Church, Atlanta, Georgia |
E75673
|
entity |
| Predicate | notableEventYear_funeralOfMLKJr |
P925
|
FINISHED |
| Object | 1968 |
—
|
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: 1968 | Statement: [Ebenezer Baptist Church, Atlanta, Georgia, notableEventYear_funeralOfMLKJr, 1968]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventYear_funeralOfMLKJr Context triple: [Ebenezer Baptist Church, Atlanta, Georgia, notableEventYear_funeralOfMLKJr, 1968]
-
A.
commemoratesPersonDeathYear
Indicates that something marks, honors, or is associated with the year in which a specific person died.
-
B.
commemoratedYear
Indicates the specific year in which an event, person, or entity is formally remembered, honored, or celebrated.
-
C.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
-
D.
notableDeath
Indicates that an entity’s death is considered significant or noteworthy in some context.
-
E.
commemoratesPersonBirthYear
Indicates that something is intended to honor or mark the year in which a specific person was born.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0da77008190922f414b85b9cad4 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb8364d848190a96a9bc7a6126af2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.