Triple
T2346996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title XVIII of the Social Security Act |
E45153
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | title of United States federal statute |
C354
|
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: title of United States federal statute Context triple: [Title XVIII of the Social Security Act, instanceOf, title of United States federal statute]
-
A.
United States federal statute
chosen
A United States federal statute is a law formally enacted by Congress and signed by the President (or passed over a veto) that applies nationwide and governs conduct, rights, and obligations under federal jurisdiction.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
state title
A state title is an official government-issued document that establishes legal ownership of a vehicle or property within a specific state jurisdiction.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
Created at: March 4, 2026, 7:52 p.m.