Triple
T15613810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multidisciplinary Accident Investigation Team |
E375362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | traffic collision investigation unit |
C945
|
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: traffic collision investigation unit Context triple: [Multidisciplinary Accident Investigation Team, instanceOf, traffic collision investigation unit]
-
A.
accident investigation
chosen
Accident investigation is the systematic process of collecting and analyzing evidence about an incident to determine its causes and contributing factors, with the goal of preventing similar events in the future.
-
B.
criminal investigation unit
A criminal investigation unit is a specialized law enforcement team responsible for systematically gathering, analyzing, and preserving evidence to identify suspects, solve crimes, and support successful prosecution.
-
C.
traffic authority
A traffic authority is an organization or governmental body responsible for planning, regulating, and managing road use, traffic flow, and transportation safety within a specific jurisdiction.
-
D.
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.
-
E.
car accident
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.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:13 a.m.