Triple
T21497237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albrecht v. Herald Co. |
E530386
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sherman Act case |
C17820
|
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: Sherman Act case Context triple: [Albrecht v. Herald Co., instanceOf, Sherman Act case]
-
A.
antitrust case
chosen
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.
-
B.
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.
-
C.
Origination Clause case
An Origination Clause case is a legal dispute that examines whether a federal tax or revenue-raising measure unconstitutionally originated in the Senate rather than the House of Representatives, as required by Article I, Section 7 of the U.S. Constitution.
-
D.
Erie doctrine case
An Erie doctrine case is a federal court lawsuit in which the court must decide whether to apply state substantive law or federal law/procedural rules under the principles established in Erie Railroad Co. v. Tompkins and its progeny.
-
E.
competition law provision
A competition law provision is a legal rule or clause designed to regulate market behavior by preventing anti-competitive practices, promoting fair competition, and protecting consumer welfare.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:23 p.m.