Triple
T27028481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleepy Lagoon murder case |
E680851
|
entity |
| Predicate | courtroomPractice |
P31966
|
FINISHED |
| Object | defendants tried en masse |
—
|
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: defendants tried en masse | Statement: [Sleepy Lagoon murder case, courtroomPractice, defendants tried en masse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtroomPractice Context triple: [Sleepy Lagoon murder case, courtroomPractice, defendants tried en masse]
-
A.
courtroom
Indicates a relationship where a legal proceeding or judicial action takes place within or is associated with a specific courtroom.
-
B.
practiceCourt
Indicates that an entity uses or is associated with a particular court for practice or training activities.
-
C.
courtEnvironment
Indicates the environmental conditions, setting, or contextual factors present in or around a court that may influence activities or outcomes there.
-
D.
courtContext
chosen
Indicates the legal or judicial setting, circumstances, or framework within which a court-related action or relationship takes place.
-
E.
courtStyle
Indicates the manner or stylistic approach in which a court conducts its proceedings or presents its decisions.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:12 a.m.