Triple
T4062937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TPWS |
E86256
|
entity |
| Predicate | effectOfActivation |
P40373
|
FINISHED |
| Object | initiates emergency brake application |
—
|
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: initiates emergency brake application | Statement: [TPWS, effectOfActivation, initiates emergency brake application]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOfActivation Context triple: [TPWS, effectOfActivation, initiates emergency brake application]
-
A.
activationMechanism
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
-
B.
tookEffect
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
-
C.
effectOnSystem
chosen
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
-
D.
usesEffectType
Indicates that an entity employs or is associated with a particular type or category of effect in its operation or behavior.
-
E.
registrationEffect
Indicates the outcome or consequence that results from an entity being registered or from the act of registration taking place.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.