Triple
T23872858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. R. Grovey |
E592773
|
entity |
| Predicate | caseHeBroughtHeardBy |
P75119
|
FINISHED |
| Object | Supreme Court of the United States |
—
|
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: Supreme Court of the United States | Statement: [R. R. Grovey, caseHeBroughtHeardBy, Supreme Court of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseHeBroughtHeardBy Context triple: [R. R. Grovey, caseHeBroughtHeardBy, Supreme Court of the United States]
-
A.
caseHeBrought
Indicates that a male subject initiated and brought a legal case or lawsuit against another party.
-
B.
heardByCourt
chosen
Indicates that a matter, case, or issue has been formally considered or examined by a court.
-
C.
hearsProceedingsBroughtBy
Indicates that a judicial or administrative body formally considers and adjudicates legal proceedings initiated by a particular party.
-
D.
hearsCasesAs
Indicates that one judicial body or judge reviews and adjudicates cases originating from another court or jurisdiction.
-
E.
hearsCasesWith
Indicates that one judicial body or judge conducts proceedings together with another judicial body or judge in hearing the same cases.
- 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfed81881909905f71377f759b1 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:14 p.m.