Triple
T1290399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Positive Train Control |
E27532
|
entity |
| Predicate | actionOnViolation |
P9769
|
FINISHED |
| Object | automatically apply brakes |
—
|
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: automatically apply brakes | Statement: [Positive Train Control, actionOnViolation, automatically apply brakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actionOnViolation Context triple: [Positive Train Control, actionOnViolation, automatically apply brakes]
-
A.
actsOn
chosen
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
B.
violatedPrinciple
Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
-
C.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
-
D.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
E.
cannotVeto
Indicates that an entity lacks the authority or ability to reject, block, or override a decision, proposal, or action made by another entity.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d6af908190ade9c481cc6f0ad8 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.