Triple
T3392571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article I – General Provisions |
E71453
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | article of the Federal Rules of Evidence |
C5085
|
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: article of the Federal Rules of Evidence Context triple: [Article I – General Provisions, instanceOf, article of the Federal Rules of Evidence]
-
A.
United States federal law
United States federal law is the body of statutes, regulations, and legal principles enacted or authorized by the federal government that governs nationwide matters under the U.S. Constitution.
-
B.
judicial rules
chosen
Judicial rules are formal guidelines and procedures established by courts to govern how legal cases are processed, decided, and managed within the judicial system.
-
C.
clause of the United States Constitution
A clause of the United States Constitution is a distinct, self-contained provision within the document that establishes specific powers, rights, limitations, or procedures governing the federal government and its relationship to the states and the people.
-
D.
federal law
A federal law is a legally binding rule or statute enacted by a national government’s legislative body that applies uniformly across all states or regions within that nation.
-
E.
United States federal law instrument
A United States federal law instrument is an official legal document or mechanism, such as a statute, regulation, executive order, or treaty, through which the federal government creates, modifies, or enforces legal obligations and 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:14 p.m.