Triple
T33635509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People v. Pratt |
E861679
|
entity |
| Predicate | hasLocationOfAllegedCrime |
P182277
|
FINISHED |
| Object | Los Angeles, California |
—
|
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: Los Angeles, California | Statement: [People v. Pratt, hasLocationOfAllegedCrime, Los Angeles, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationOfAllegedCrime Context triple: [People v. Pratt, hasLocationOfAllegedCrime, Los Angeles, California]
-
A.
positionOnCrime
Indicates a stance, opinion, or policy position that an entity holds regarding crime or crime-related issues.
-
B.
allegedMisconductLocation
chosen
Indicates the place where the alleged misconduct is reported to have occurred.
-
C.
allegedAssaultLocation
Indicates the place where an assault is claimed or reported to have occurred, without asserting that the assault actually happened.
-
D.
hasCrimeScene
Indicates that a particular location or setting is the site where a specific crime occurred or was discovered.
-
E.
crimeLocation
Indicates that a crime occurred at, or is associated with, a particular location.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 1, 2026, 1:42 a.m.