Triple
T9159278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | living tree doctrine |
E219780
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | principle of constitutional interpretation |
C2144
|
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: principle of constitutional interpretation Context triple: [living tree doctrine, instanceOf, principle of constitutional interpretation]
-
A.
constitutional interpreter
A constitutional interpreter is an entity—such as a judge, scholar, or institution—that analyzes and applies the text, structure, history, and principles of a constitution to resolve legal and political questions.
-
B.
constitutional law
Constitutional law is the body of legal principles and rules that defines the structure, powers, and limits of government and protects fundamental rights under a nation's constitution.
-
C.
constitutional concept
chosen
A constitutional concept is an abstract legal and political idea that defines, structures, or constrains the organization, powers, and fundamental principles of a constitutional system.
-
D.
constitutional law topic
A constitutional law topic is a specific subject area concerning the interpretation, application, or structure of a nation's constitution, including the distribution of governmental powers and the protection of individual rights.
-
E.
source of constitutional law
A source of constitutional law is any authoritative origin—such as a written constitution, judicial decisions, conventions, or scholarly writings—from which the fundamental rules and principles governing a state’s constitutional order are derived.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:21 p.m.