Triple
T9808283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vikram |
E238205
|
entity |
| Predicate | failureEvent |
P90111
|
FINISHED |
| Object | lost contact during final descent |
—
|
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: lost contact during final descent | Statement: [Vikram, failureEvent, lost contact during final descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failureEvent Context triple: [Vikram, failureEvent, lost contact during final descent]
-
A.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
B.
failureBehavior
Indicates how a system, component, or process is expected to respond or act when a failure or error condition occurs.
-
C.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
D.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
E.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7ddaac8190a5584a5c863fbaa3 |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:29 p.m.