Triple
T13855691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judiciary Act of 1801 |
E333056
|
entity |
| Predicate | setSupremeCourtSizeTo |
P111782
|
FINISHED |
| Object | 5 justices upon next vacancy |
—
|
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: 5 justices upon next vacancy | Statement: [Judiciary Act of 1801, setSupremeCourtSizeTo, 5 justices upon next vacancy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setSupremeCourtSizeTo Context triple: [Judiciary Act of 1801, setSupremeCourtSizeTo, 5 justices upon next vacancy]
-
A.
numberOfSupremeCourtJustices
Indicates the total count of individuals serving as justices on a specified Supreme Court.
-
B.
supremeCourtComposition
Indicates the specific makeup or set of justices serving on a supreme court at a given time.
-
C.
majorityJusticesCount
Indicates the number of justices whose votes form the majority in a judicial decision.
-
D.
maximumNumberOfJustices
Indicates the total number of justices that is allowed or prescribed as the upper limit for a given judicial body.
-
E.
definedNumberOfAssociateJustices
Indicates that an entity specifies or establishes the exact number of associate justices in a particular judicial body or court.
- F. None of above. chosen
Provenance (4 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02db9c9c81909bb2d2fbfb7394b1 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:14 p.m.