Triple
T11103410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal enclaves doctrine |
E262566
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States federal law doctrine |
C568
|
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: United States federal law doctrine Context triple: [Federal enclaves doctrine, instanceOf, United States federal law doctrine]
-
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.
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.
-
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.
United States federal statute
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.
-
E.
legal doctrine
chosen
A legal doctrine is a principle or framework developed through statutes, judicial decisions, and scholarly interpretation that guides how laws are understood, applied, and evolved in legal systems.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.