Triple
T13855690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judiciary Act of 1801 |
E333056
|
entity |
| Predicate | changedNumberOf |
P111781
|
FINISHED |
| Object | Supreme Court 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: Supreme Court justices | Statement: [Judiciary Act of 1801, changedNumberOf, Supreme Court justices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedNumberOf Context triple: [Judiciary Act of 1801, changedNumberOf, Supreme Court justices]
-
A.
changedAfter
Indicates that one entity underwent a change at a point in time that is later than the time at which another referenced entity changed.
-
B.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
C.
changesWith
Indicates that one entity varies or is modified in response to changes in another entity.
-
D.
changedUnder
Indicates that one entity has undergone alteration, modification, or transformation as a result of the influence, action, or conditions imposed by another entity.
-
E.
changedOn
Indicates that an entity underwent a modification or update at a specific point in time.
- 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.