Triple
T3392700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article IV – Relevance and Its Limits |
E71456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of the U.S. Federal Rules of Evidence |
C2873
|
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: section of the U.S. Federal Rules of Evidence Context triple: [Article IV – Relevance and Its Limits, instanceOf, section of the U.S. Federal Rules of Evidence]
-
A.
section of a legal document
chosen
A section of a legal document is a distinct, numbered subdivision that organizes related provisions, rights, and obligations under a specific heading within the overall legal text.
-
B.
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.
-
C.
judicial rules
Judicial rules are formal guidelines and procedures established by courts to govern how legal cases are processed, decided, and managed within the judicial system.
-
D.
section of the Congressional Record
A section of the Congressional Record is a distinct, thematically or procedurally organized portion of the official published account of the proceedings and debates of the United States Congress.
-
E.
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.
- 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.