Triple
T9231267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judiciary Act of 1869 |
E221820
|
entity |
| Predicate | requiredEachJusticeToSitOnCircuitsPerYear |
P87697
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Judiciary Act of 1869, requiredEachJusticeToSitOnCircuitsPerYear, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredEachJusticeToSitOnCircuitsPerYear Context triple: [Judiciary Act of 1869, requiredEachJusticeToSitOnCircuitsPerYear, 1]
-
A.
minimumNumberOfJustices
Indicates the smallest number of justices required for a court or judicial body to validly conduct its proceedings or make decisions.
-
B.
majorityJusticesCount
Indicates the number of justices whose votes form the majority in a judicial decision.
-
C.
maximumNumberOfJustices
Indicates the total number of justices that is allowed or prescribed as the upper limit for a given judicial body.
-
D.
termLengthOfJustices
Indicates the duration of time that justices serve in their official positions.
-
E.
numberOfJudges
Indicates the total count of judges associated with a particular case, event, or entity.
- 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_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. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:29 p.m.