Triple
T28684319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judiciary Reorganization Bill of 1937 |
E726088
|
entity |
| Predicate | proposedSupremeCourtSizeLimit |
P12829
|
FINISHED |
| Object | 15 justices |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 15 justices | Statement: [Judiciary Reorganization Bill of 1937, proposedSupremeCourtSizeLimit, 15 justices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedSupremeCourtSizeLimit Context triple: [Judiciary Reorganization Bill of 1937, proposedSupremeCourtSizeLimit, 15 justices]
-
A.
setSupremeCourtSizeTo
Indicates setting the number of seats or justices on a supreme court to a specified size.
-
B.
numberOfSupremeCourtJustices
Indicates the total count of individuals serving as justices on a specified Supreme Court.
-
C.
maximumNumberOfJustices
chosen
Indicates the total number of justices that is allowed or prescribed as the upper limit for a given judicial body.
-
D.
supremeCourtComposition
Indicates the specific makeup or set of justices serving on a supreme court at a given time.
-
E.
majorityJusticesCount
Indicates the number of justices whose votes form the majority in a judicial decision.
- F. None of above.
Provenance (3 batches)
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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 5:11 a.m.