Triple
T4421720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subtitle III – Financial Management |
E95113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | portion of Title 31, United States Code |
C250
|
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: portion of Title 31, United States Code Context triple: [Subtitle III – Financial Management, instanceOf, portion of Title 31, United States Code]
-
A.
title of the Code of Federal Regulations
The title of the Code of Federal Regulations is the top-level organizational division that groups together all federal regulations pertaining to a broad subject area, such as labor, environment, or transportation.
-
B.
subtitle of the Internal Revenue Code
A subtitle of the Internal Revenue Code is a major organizational division that groups together related tax laws and provisions under a broad subject area within the Code.
-
C.
title of the California Code of Regulations
The title of the California Code of Regulations is the official, numbered major division that organizes and identifies a broad subject area within the state's administrative regulations.
-
D.
United States federal law
chosen
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.
-
E.
component of the United States Court of Federal Claims
A component of the United States Court of Federal Claims is an organizational unit or functional division within the court that supports its judicial mission, such as through case management, administration, or specialized legal services.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:30 p.m.