Triple
T32152199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Leroy Washington |
E821188
|
entity |
| Predicate | petitionedCourt |
P124421
|
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: [David Leroy Washington, petitionedCourt, Supreme Court of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: petitionedCourt Context triple: [David Leroy Washington, petitionedCourt, Supreme Court of the United States]
-
A.
destinationCourt
chosen
Indicates the court or judicial body to which a case, appeal, or legal matter is directed or transferred.
-
B.
courtName
Indicates the official name assigned to a particular court within a legal or judicial system.
-
C.
decisionCourt
Indicates that a particular court rendered the decision or judgment in a given legal case or proceeding.
-
D.
courtNumber
Indicates the specific numbered court (e.g., field, room, or venue) assigned or associated with an event, case, or match.
-
E.
involvedCourt
Indicates that a specific court participates in, has jurisdiction over, or is otherwise formally associated with a given legal case or proceeding.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9eccab88190a2895cbb0332c5a7 |
completed | May 3, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:31 a.m.