Triple
T1349133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baker v. Nelson |
E28840
|
entity |
| Predicate | resultForPlaintiffs |
P2931
|
FINISHED |
| Object | relief denied |
—
|
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: relief denied | Statement: [Baker v. Nelson, resultForPlaintiffs, relief denied]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultForPlaintiffs Context triple: [Baker v. Nelson, resultForPlaintiffs, relief denied]
-
A.
legalOutcome
chosen
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
B.
juryProvidedBy
Indicates that a particular jury is supplied, appointed, or made available by a specified source or authority.
-
C.
resultDetermination
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
-
D.
affectedCourt
Indicates that a particular court is impacted or influenced by a specified action, decision, or legal matter.
-
E.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c268745481908be649526c18e558 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.