Triple
T15358307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 New Jersey Turnpike collision |
E367220
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road traffic collision |
C334
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: road traffic collision Context triple: [2014 New Jersey Turnpike collision, instanceOf, road traffic collision]
-
A.
car accident
chosen
A car accident is an unexpected collision or incident involving one or more motor vehicles that results in damage, injury, or disruption to normal traffic flow.
-
B.
train collision
A train collision is an accident in which one or more trains impact each other or another object on or near the tracks, often resulting in significant damage, disruption, and potential injury or loss of life.
-
C.
traffic plaza
A traffic plaza is a designed open area, often at an intersection or junction, that organizes and manages the flow of vehicles and pedestrians while sometimes providing public space amenities.
-
D.
rail accident
A rail accident is an unintended event involving trains or railway infrastructure that results in damage, disruption, injury, or loss of life.
-
E.
road traffic agreement
A road traffic agreement is a formal arrangement between parties—such as governments, municipalities, or private entities—that defines rights, responsibilities, and rules for the use, management, and regulation of road traffic within a specified area or network.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 10, 2026, 3:18 a.m.