Triple
T33714299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christy Brzonkala v. Antonio J. Morrison et al. |
E863826
|
entity |
| Predicate | decidedUnder |
P177238
|
FINISHED |
| Object | Rehnquist Court |
—
|
NE NERFINISHED |
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: Rehnquist Court | Statement: [Christy Brzonkala v. Antonio J. Morrison et al., decidedUnder, Rehnquist Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidedUnder Context triple: [Christy Brzonkala v. Antonio J. Morrison et al., decidedUnder, Rehnquist Court]
-
A.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
B.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
-
C.
wasDecidedBy
Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
-
D.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
E.
deciderOf
Indicates that one entity is the one who makes decisions or choices regarding another entity or situation.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae2a7a8819099945d1706a94bfd |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:44 a.m.