Triple
T6732980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATB-EG |
E153680
|
entity |
| Predicate | riskMitigated |
P28689
|
FINISHED |
| Object | train collisions |
—
|
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: train collisions | Statement: [ATB-EG, riskMitigated, train collisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskMitigated Context triple: [ATB-EG, riskMitigated, train collisions]
-
A.
riskAddressed
chosen
Indicates that a particular risk has been identified and is being mitigated, managed, or otherwise handled by an associated action, control, or measure.
-
B.
riskBased
Indicates that something is determined, prioritized, or managed according to the level or assessment of risk involved.
-
C.
riskElement
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
-
D.
riskTaken
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
-
E.
riskBasis
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
- 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:09 p.m.