Triple
T15358343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 New Jersey Turnpike collision |
E367220
|
entity |
| Predicate | truckDriverCharge |
P118258
|
FINISHED |
| Object | vehicular homicide |
—
|
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: vehicular homicide | Statement: [2014 New Jersey Turnpike collision, truckDriverCharge, vehicular homicide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: truckDriverCharge Context triple: [2014 New Jersey Turnpike collision, truckDriverCharge, vehicular homicide]
-
A.
appliesTollTo
Indicates that a fee or charge is imposed on a subject for using, accessing, or passing through something.
-
B.
hasToll
Indicates that the use, access, or passage associated with something requires payment of a toll or fee.
-
C.
fareCalculation
Indicates the process or method used to determine the monetary cost of a trip or service based on specified pricing rules and conditions.
-
D.
hasTollSegment
Indicates that a route, road, or path includes a segment where a toll must be paid.
-
E.
chargesFeeFor
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
- F. None of above. chosen
Provenance (4 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e2d4934819097fc63603964217c |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:18 a.m.