Triple
T15666971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kishor S. Trivedi |
E377210
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object |
Reliability and Availability Engineering: Modeling, Analysis, and Applications
"Reliability and Availability Engineering: Modeling, Analysis, and Applications" is a comprehensive technical book that presents theoretical foundations and practical methods for analyzing, modeling, and improving the reliability and availability of engineering systems.
|
E1170209
|
NE FINISHED |
How this triple was built (4 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: Reliability and Availability Engineering: Modeling, Analysis, and Applications | Statement: [Kishor S. Trivedi, notableWork, Reliability and Availability Engineering: Modeling, Analysis, and Applications]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Reliability and Availability Engineering: Modeling, Analysis, and Applications Context triple: [Kishor S. Trivedi, notableWork, Reliability and Availability Engineering: Modeling, Analysis, and Applications]
-
A.
Lusser's law of series system reliability
Lusser's law of series system reliability is a principle in reliability engineering stating that the overall reliability of a series system equals the product of the reliabilities of its individual components, causing system reliability to decrease as more components are added.
-
B.
reliability engineering
Reliability engineering is an engineering discipline focused on ensuring systems and components perform their intended functions dependably over time by analyzing, predicting, and improving their failure behavior.
-
C.
Failure Mode and Effects Analysis
Failure Mode and Effects Analysis is a systematic, proactive method for identifying potential failures in a process, product, or system and evaluating their causes and effects to prioritize and mitigate risk.
-
D.
Reliability Enhancement and Re-engining Program
The Reliability Enhancement and Re-engining Program is a major U.S. Air Force initiative to upgrade and extend the service life of C-5 Galaxy transport aircraft by improving their engines, systems, and overall performance.
-
E.
Queueing Systems, Volume 1: Theory
Queueing Systems, Volume 1: Theory is a foundational textbook by Leonard Kleinrock that rigorously develops the mathematical theory of queueing processes and their applications in communication and computer systems.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Reliability and Availability Engineering: Modeling, Analysis, and Applications Triple: [Kishor S. Trivedi, notableWork, Reliability and Availability Engineering: Modeling, Analysis, and Applications]
Generated description
"Reliability and Availability Engineering: Modeling, Analysis, and Applications" is a comprehensive technical book that presents theoretical foundations and practical methods for analyzing, modeling, and improving the reliability and availability of engineering systems.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Reliability and Availability Engineering: Modeling, Analysis, and Applications Target entity description: "Reliability and Availability Engineering: Modeling, Analysis, and Applications" is a comprehensive technical book that presents theoretical foundations and practical methods for analyzing, modeling, and improving the reliability and availability of engineering systems.
-
A.
Lusser's law of series system reliability
Lusser's law of series system reliability is a principle in reliability engineering stating that the overall reliability of a series system equals the product of the reliabilities of its individual components, causing system reliability to decrease as more components are added.
-
B.
reliability engineering
Reliability engineering is an engineering discipline focused on ensuring systems and components perform their intended functions dependably over time by analyzing, predicting, and improving their failure behavior.
-
C.
Failure Mode and Effects Analysis
Failure Mode and Effects Analysis is a systematic, proactive method for identifying potential failures in a process, product, or system and evaluating their causes and effects to prioritize and mitigate risk.
-
D.
Reliability Enhancement and Re-engining Program
The Reliability Enhancement and Re-engining Program is a major U.S. Air Force initiative to upgrade and extend the service life of C-5 Galaxy transport aircraft by improving their engines, systems, and overall performance.
-
E.
Queueing Systems, Volume 1: Theory
Queueing Systems, Volume 1: Theory is a foundational textbook by Leonard Kleinrock that rigorously develops the mathematical theory of queueing processes and their applications in communication and computer systems.
- F. None of above. chosen
Provenance (5 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f1151548190a14607e762686cb1 |
completed | April 16, 2026, 2:53 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff67a22888819092ea521bbad7bcb7 |
completed | May 9, 2026, 4:58 p.m. |
| NEDg | Description generation | batch_69ff68fd16b88190a78772bcd0302189 |
completed | May 9, 2026, 5:03 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ff6943d47881908c1634b43a6d6b96 |
completed | May 9, 2026, 5:05 p.m. |
Created at: April 10, 2026, 4:16 a.m.