Triple
T9309076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cutter |
E223962
|
entity |
| Predicate | caseOutcomeForPetitioner |
P2931
|
FINISHED |
| Object | prevailing party at the Supreme Court |
—
|
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: prevailing party at the Supreme Court | Statement: [Cutter, caseOutcomeForPetitioner, prevailing party at the Supreme Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseOutcomeForPetitioner Context triple: [Cutter, caseOutcomeForPetitioner, prevailing party at the Supreme Court]
-
A.
legalOutcome
chosen
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
B.
councilOutcome
Indicates the result or decision produced by a council after its deliberation or proceedings.
-
C.
caseDecidedBy
Indicates that a legal case is resolved or adjudicated by a specific decision-making authority, such as a judge or court.
-
D.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
E.
governsOutcome
Indicates that one entity has decisive control or influence over the result or consequence affecting another entity.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1daba67c819081d53545d67ef127 |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.