Triple
T23591343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whiting |
E582484
|
entity |
| Predicate | hearingCourt |
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: [Whiting, hearingCourt, Supreme Court of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hearingCourt Context triple: [Whiting, hearingCourt, Supreme Court of the United States]
-
A.
heardByCourt
chosen
Indicates that a matter, case, or issue has been formally considered or examined by a court.
-
B.
courtHeld
Indicates that a court has formally decided, ruled, or determined a particular legal issue or question.
-
C.
heldCourtIn
Indicates that an authority or governing body formally conducted judicial or official proceedings in a particular place.
-
D.
hearsAppealsIn
Indicates that a judicial body has the authority to review and decide appeals within a specified jurisdiction or court.
-
E.
heldCourtUnder
Indicates that one authority conducted judicial or ceremonial court proceedings under the jurisdiction, auspices, or authority of another.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b035a5d88190bd2e1fa0170045cd |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.