Triple
T27028466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleepy Lagoon murder case |
E680851
|
entity |
| Predicate | appellateCourtDecision |
P113433
|
FINISHED |
| Object | convictions reversed |
—
|
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: convictions reversed | Statement: [Sleepy Lagoon murder case, appellateCourtDecision, convictions reversed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appellateCourtDecision Context triple: [Sleepy Lagoon murder case, appellateCourtDecision, convictions reversed]
-
A.
decisionCourt
Indicates that a particular court rendered the decision or judgment in a given legal case or proceeding.
-
B.
hasLowerCourtDecision
Indicates that a higher court case is associated with, or results from, a specific decision made by a lower court.
-
C.
chiefJusticeAtDecision
Indicates that the specified person was serving as the chief justice at the time a particular decision was made.
-
D.
appellateInstance
Indicates that one legal proceeding or court serves as the appellate (reviewing) instance for another lower-level decision or case.
-
E.
appellateBodyFound
chosen
Indicates that an appellate body has reached and recorded a decision or finding regarding a prior judgment or ruling.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6223409688190959248db2146e527 |
completed | May 2, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7:12 a.m.