Triple
T9231261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judiciary Act of 1869 |
E221820
|
entity |
| Predicate | fixedSupremeCourtSizeAt |
P26911
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [Judiciary Act of 1869, fixedSupremeCourtSizeAt, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fixedSupremeCourtSizeAt Context triple: [Judiciary Act of 1869, fixedSupremeCourtSizeAt, 9]
-
A.
numberOfSupremeCourtJustices
chosen
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.
definedNumberOfAssociateJustices
Indicates that an entity specifies or establishes the exact number of associate justices in a particular judicial body or court.
-
E.
supremeCourtOf
Indicates that one entity serves as the highest judicial authority (supreme court) within the jurisdiction or legal system of another entity.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee190204819096b38270a0abc116 |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:29 p.m.