Triple
T17343340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AF4590 |
E421118
|
entity |
| Predicate | engineFailure |
P127112
|
FINISHED |
| Object | loss of thrust on engines 1 and 2 |
—
|
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: loss of thrust on engines 1 and 2 | Statement: [AF4590, engineFailure, loss of thrust on engines 1 and 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineFailure Context triple: [AF4590, engineFailure, loss of thrust on engines 1 and 2]
-
A.
engine
Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
-
B.
fuelCellIssue
Indicates that there is a problem, malfunction, or abnormal condition affecting a fuel cell or its operation.
-
C.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
D.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
E.
engineReliability
Indicates how consistently and dependably an engine performs its intended function without failure over time.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a18aca88190a816da85dd5fe371 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:44 a.m.