Triple
T32732300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Bastard |
E836985
|
entity |
| Predicate | hasAccidentDate |
P81161
|
FINISHED |
| Object | 1955-09-30 |
—
|
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: 1955-09-30 | Statement: [Little Bastard, hasAccidentDate, 1955-09-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccidentDate Context triple: [Little Bastard, hasAccidentDate, 1955-09-30]
-
A.
hasAccidentAt
Indicates that an accident involving a subject occurs at a specific location or time.
-
B.
firstAccidentDate
chosen
Indicates the date on which an entity experienced its first recorded accident.
-
C.
accidentOccurredDuring
Indicates that an accident took place within the time span or context of a specified event, activity, or condition.
-
D.
dateOfAccidentInvestigated
Indicates that a specific accident has been examined or investigated on a particular date.
-
E.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
- 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_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 1:11 a.m.