Triple
T776881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Browder v. Gayle |
E16404
|
entity |
| Predicate | defendantDescription |
P2238
|
FINISHED |
| Object | Mayor of Montgomery, Alabama |
—
|
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: Mayor of Montgomery, Alabama | Statement: [Browder v. Gayle, defendantDescription, Mayor of Montgomery, Alabama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendantDescription Context triple: [Browder v. Gayle, defendantDescription, Mayor of Montgomery, Alabama]
-
A.
defendant
chosen
Indicates that an entity is the party accused or sued in a legal action or proceeding.
-
B.
typeOfDefense
Indicates the specific kind or category of defense employed or possessed in a given context.
-
C.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
D.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
E.
subjectOfProsecution
Indicates that an entity is the target or focus of a legal prosecution or criminal proceeding initiated by an authority.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a50a443481909ae3662764ee69a4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.