Triple
T20760056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Susan B. Anthony |
E510953
|
entity |
| Predicate | defendantResponseToFine |
P141392
|
FINISHED |
| Object | refused to pay the fine |
—
|
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: refused to pay the fine | Statement: [United States v. Susan B. Anthony, defendantResponseToFine, refused to pay the fine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendantResponseToFine Context triple: [United States v. Susan B. Anthony, defendantResponseToFine, refused to pay the fine]
-
A.
defendant
Indicates that an entity is the party accused or sued in a legal action or proceeding.
-
B.
defendantStatus
Indicates the legal condition or standing of a defendant within a judicial or law-enforcement process.
-
C.
defendantPosition
Indicates the role, stance, or location that a defendant holds within a legal case or proceeding.
-
D.
coDefendant
Indicates that two or more parties are jointly named and involved as defendants in the same legal case or proceeding.
-
E.
respondentPosition
Indicates the role, title, or job position held by a respondent in the context of a survey, study, or inquiry.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24751688190829f9d836abfb606 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:35 p.m.