Triple
T22380463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revised Statutes of the United States |
E553259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | codification of federal statutes |
C41977
|
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: codification of federal statutes Context triple: [Revised Statutes of the United States, instanceOf, codification of federal statutes]
-
A.
codification project
chosen
A codification project is a structured initiative to systematically collect, organize, and formalize dispersed knowledge, rules, or practices into a coherent, accessible, and standardized body of documentation.
-
B.
canonical legislation
Canonical legislation is the body of laws and regulations established by ecclesiastical authority to govern the doctrine, discipline, and administration of a religious institution, particularly within the Christian tradition.
-
C.
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.
-
D.
codification and progressive development instrument
A codification and progressive development instrument is a formal legal or policy tool designed to systematically organize existing rules and principles while simultaneously advancing and refining them to address emerging needs and gaps.
-
E.
recueil législatif
Un recueil législatif est une compilation organisée de textes de loi et de règlements, généralement classés par thème, date ou juridiction, destinée à faciliter la consultation du droit en vigueur.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.