Triple
T4758028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. One Book Called Ulysses |
E105634
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | obscenity case |
C11038
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: obscenity case Context triple: [United States v. One Book Called Ulysses, instanceOf, obscenity case]
-
A.
sexual misconduct scandal
A sexual misconduct scandal is a widely publicized controversy involving allegations or revelations of inappropriate, non-consensual, or exploitative sexual behavior by an individual or group, often leading to public outrage, legal consequences, and reputational damage.
-
B.
media scandal
A media scandal is a widely publicized controversy, often involving alleged wrongdoing or ethical breaches by public figures or institutions, that attracts intense and sustained news coverage and public scrutiny.
-
C.
free speech case
chosen
A free speech case is a legal dispute that centers on whether an individual’s or group’s expression is protected under constitutional or statutory guarantees of freedom of speech.
-
D.
contentious case
A contentious case is a legal dispute between opposing parties brought before a court or tribunal for adjudication on contested rights or obligations.
-
E.
crimeAgainstHumanity
A crimeAgainstHumanity is a widespread or systematic attack directed against any civilian population, committed with knowledge of the attack, involving acts such as murder, enslavement, deportation, torture, or other inhumane conduct that severely violates fundamental human rights.
- F. None of above.
Provenance (1 batch)
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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:20 p.m.