Triple
T4600084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MyISAM storage engine |
E100301
|
entity |
| Predicate | crashRecovery |
P42320
|
FINISHED |
| Object | non-automatic |
—
|
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: non-automatic | Statement: [MyISAM storage engine, crashRecovery, non-automatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crashRecovery Context triple: [MyISAM storage engine, crashRecovery, non-automatic]
-
A.
errorRecovery
Indicates that an entity detects a failure or error condition and initiates actions to restore normal or acceptable operation.
-
B.
recovery
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
-
C.
recoveryCapability
chosen
Indicates the ability of an entity to return to a normal or functional state after experiencing damage, failure, or disruption.
-
D.
recoveryPlan
Indicates a planned set of actions or strategies designed to restore a system, entity, or situation from a degraded, failed, or disrupted state back to an acceptable or normal condition.
-
E.
launchAndRecovery
Indicates a relationship where one entity is responsible for both deploying (launching) another entity into operation and subsequently retrieving (recovering) it afterward.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5971f448819090f6e76c7d3ffc2d |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.