Triple
T11055109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific States Telephone & Telegraph Co. v. Oregon |
E261353
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political question doctrine case |
C734
|
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: political question doctrine case Context triple: [Pacific States Telephone & Telegraph Co. v. Oregon, instanceOf, political question doctrine case]
-
A.
public policy doctrine
A public policy doctrine is a legal principle that allows courts or governments to limit, invalidate, or shape actions, contracts, or decisions that conflict with the broader interests, values, or welfare of society.
-
B.
constitutional law case
chosen
A constitutional law case is a legal dispute that requires a court to interpret and apply a nation's constitution to determine the validity of government actions, laws, or policies.
-
C.
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.
-
D.
legal doctrine
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.
-
E.
public policy controversy
A public policy controversy is a sustained, often polarized dispute among stakeholders over the goals, design, implementation, or consequences of government actions or regulations.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:26 p.m.