Triple
T15059448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flood v. Kuhn |
E379586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landmark antitrust case |
C733
|
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: landmark antitrust case Context triple: [Flood v. Kuhn, instanceOf, landmark antitrust case]
-
A.
landmark case
chosen
A landmark case is a court decision that establishes a significant new legal principle or precedent, often reshaping the interpretation or application of the law.
-
B.
antitrust case
An antitrust case is a legal action in which government agencies or private parties challenge business practices alleged to unlawfully restrict competition, create monopolies, or otherwise violate competition laws.
-
C.
landmark decision
A landmark decision is a court ruling that establishes a significant new legal principle or precedent, often reshaping the interpretation or application of the law.
-
D.
antitrust agreement
An antitrust agreement is a formal or informal arrangement between two or more independent economic entities that coordinates their competitive behavior in a way that may restrict competition, such as fixing prices, limiting output, or dividing markets.
-
E.
Reconstruction-era case
A Reconstruction-era case is a legal dispute arising during the post–Civil War period (circa 1865–1877) that addresses issues related to federal authority, civil rights, and the reintegration of former Confederate states into the Union.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:01 a.m.