Triple
T16180046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABS |
E392659
|
entity |
| Predicate | failsSafeTo |
P122019
|
FINISHED |
| Object | conventional braking when inoperative |
—
|
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: conventional braking when inoperative | Statement: [ABS, failsSafeTo, conventional braking when inoperative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failsSafeTo Context triple: [ABS, failsSafeTo, conventional braking when inoperative]
-
A.
failsTo
Indicates that an expected action, process, or condition does not successfully occur or is not fulfilled.
-
B.
safeToRepeat
Indicates that performing the same action or operation again under the current conditions is considered acceptable and will not cause harm or undesired effects.
-
C.
failsWhen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
-
D.
previouslySafeFor
Indicates that something was considered safe for a particular entity or use at an earlier time, but that safety status may no longer hold.
-
E.
safeOrMarginal
Indicates that the relationship or condition is classified as either clearly safe or only marginally acceptable, but not unsafe.
- F. None of above. chosen
Provenance (4 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205b88b481908ecdd8d663dc668b |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.