Triple
T2533079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smith Act |
E56206
|
entity |
| Predicate | usedToProsecute |
P23171
|
FINISHED |
| Object | members of the Communist Party USA |
—
|
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: members of the Communist Party USA | Statement: [Smith Act, usedToProsecute, members of the Communist Party USA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToProsecute Context triple: [Smith Act, usedToProsecute, members of the Communist Party USA]
-
A.
prosecuted
Indicates that legal authorities have formally brought criminal charges against an entity and pursued a case against them in a court of law.
-
B.
subjectOfProsecution
Indicates that an entity is the target or focus of a legal prosecution or criminal proceeding initiated by an authority.
-
C.
usedInCourts
chosen
Indicates that something is employed or applied within legal court settings, such as in judicial proceedings or courtroom processes.
-
D.
usedCourt
Indicates that an entity made use of or participated in legal proceedings within a particular court.
-
E.
notableProsecutor
Indicates that the person served as a prosecutor in a way that is widely recognized as significant or noteworthy.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd27afe7c8190984e10d3f3d5586b |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.