Triple
T32732301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Bastard |
E836985
|
entity |
| Predicate | hasAccidentLocation |
P26084
|
FINISHED |
| Object | near Cholame, California |
—
|
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: near Cholame, California | Statement: [Little Bastard, hasAccidentLocation, near Cholame, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccidentLocation Context triple: [Little Bastard, hasAccidentLocation, near Cholame, California]
-
A.
hasAccidentAt
Indicates that an accident involving a subject occurs at a specific location or time.
-
B.
siteOfAccident
chosen
Indicates the location where an accident occurred.
-
C.
accidentOccurredDuring
Indicates that an accident took place within the time span or context of a specified event, activity, or condition.
-
D.
hasModeOfTransportInAccident
Indicates that a specific mode of transport was involved in an accident associated with the given entity.
-
E.
involvedInAccident
Indicates that an entity participated in, was affected by, or was otherwise a party to a specific accident or collision event.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 1:11 a.m.