Triple
T36509796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bizarre Plantation scandal |
E899867
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 19th-century scandal |
C61325
|
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: 19th-century scandal Context triple: [Bizarre Plantation scandal, instanceOf, 19th-century scandal]
-
A.
19th-century controversy
A 19th-century controversy is a significant public dispute or prolonged debate during the 1800s, often involving social, political, scientific, or religious issues that shaped contemporary thought and policy.
-
B.
British legal scandal
A British legal scandal is a high-profile controversy arising from alleged misconduct, corruption, or serious procedural failures within the United Kingdom’s legal or judicial system that undermines public trust in the rule of law.
-
C.
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.
-
D.
public scandal
chosen
A public scandal is a widely known event or series of actions involving perceived wrongdoing or moral failure by individuals or institutions that provokes strong public outrage and media attention.
-
E.
religious scandal
A religious scandal is a public controversy involving misconduct, hypocrisy, or abuse within a religious institution or by its leaders that undermines moral authority and public trust.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.