Triple
T37978084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama |
E947476
|
entity |
| Predicate | civilRightsLandmark |
P144030
|
FINISHED |
| Object | Edmund Pettus Bridge in Selma |
—
|
NE NERFINISHED |
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: Edmund Pettus Bridge in Selma | Statement: [Alabama, civilRightsLandmark, Edmund Pettus Bridge in Selma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilRightsLandmark Context triple: [Alabama, civilRightsLandmark, Edmund Pettus Bridge in Selma]
-
A.
civilRightsPartner
Indicates a partnership or collaborative relationship focused on advancing or supporting civil rights initiatives or advocacy.
-
B.
civilRightsImpact
Indicates how an action, policy, or event affects the civil rights or civil liberties of individuals or groups.
-
C.
civilRightsOrganizationInvolved
Indicates that a civil rights organization is actively involved in or associated with a particular event, case, action, or situation.
-
D.
hasCivilRightsHistory
chosen
Indicates that an entity is associated with events, actions, or significance in the history of civil rights movements or struggles.
-
E.
landmarkCase
Indicates that a legal case is historically significant or precedent-setting within a legal system.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.