Triple
T14311678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sibbach v. Wilson & Co. |
E354847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal civil procedure case |
C4803
|
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: federal civil procedure case Context triple: [Sibbach v. Wilson & Co., instanceOf, federal civil procedure case]
-
A.
federal court
A federal court is a judicial body established by a national government with authority to hear and decide cases arising under that nation’s constitution, federal laws, and treaties.
-
B.
federal jurisdiction case
A federal jurisdiction case is a legal dispute that is heard in a federal court because it involves federal laws, the U.S. Constitution, the federal government, or parties from different states meeting specific jurisdictional requirements.
-
C.
federal civil enforcement action
A federal civil enforcement action is a non-criminal lawsuit brought by a U.S. federal agency or the Department of Justice to compel compliance with federal laws, regulations, or orders and to obtain remedies such as injunctions, penalties, or restitution.
-
D.
legal proceeding
chosen
A legal proceeding is a formal process conducted by a court or authorized tribunal to resolve disputes, determine rights and obligations, or enforce laws through established legal procedures.
-
E.
federal district
A federal district is a distinct territorial unit under the direct jurisdiction of a national government, separate from any constituent state or province, typically established to house the nation's capital or serve special administrative purposes.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:12 a.m.