Triple
T17175623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axel van Lamsweerde |
E416850
|
entity |
| Predicate | notableWork |
P4
|
FINISHED |
| Object |
Requirements Engineering: From System Goals to UML Models to Software Specifications
Requirements Engineering: From System Goals to UML Models to Software Specifications is a comprehensive textbook that systematically covers the processes, methods, and modeling techniques for eliciting, analyzing, and specifying software system requirements.
|
E1254562
|
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: Requirements Engineering: From System Goals to UML Models to Software Specifications | Statement: [Axel van Lamsweerde, notableWork, Requirements Engineering: From System Goals to UML Models to Software Specifications]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Requirements Engineering: From System Goals to UML Models to Software Specifications Context triple: [Axel van Lamsweerde, notableWork, Requirements Engineering: From System Goals to UML Models to Software Specifications]
-
A.
The Unified Modeling Language Reference Manual
The Unified Modeling Language Reference Manual is a comprehensive technical guide that defines and explains the UML standard for modeling software and systems.
-
B.
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach is a foundational software engineering textbook by Ivar Jacobson that popularized use-case–driven, object-oriented analysis and design methods.
-
C.
Object-Oriented Analysis and Design with Applications
Object-Oriented Analysis and Design with Applications is a foundational software engineering book by Grady Booch that systematically presents object-oriented concepts, methods, and practical design techniques.
-
D.
Essence: The Software Engineering Method
"Essence: The Software Engineering Method" is a framework introduced by Ivar Jacobson that defines a common, lightweight kernel and language for describing and improving software engineering practices.
-
E.
A Discipline for Software Engineering
"A Discipline for Software Engineering" is a book by Watts S. Humphrey that introduces and explains the Personal Software Process (PSP), a structured methodology for individual software engineers to improve the quality and predictability of their work.
- 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: Requirements Engineering: From System Goals to UML Models to Software Specifications Triple: [Axel van Lamsweerde, notableWork, Requirements Engineering: From System Goals to UML Models to Software Specifications]
Generated description
Requirements Engineering: From System Goals to UML Models to Software Specifications is a comprehensive textbook that systematically covers the processes, methods, and modeling techniques for eliciting, analyzing, and specifying software system requirements.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Requirements Engineering: From System Goals to UML Models to Software Specifications Target entity description: Requirements Engineering: From System Goals to UML Models to Software Specifications is a comprehensive textbook that systematically covers the processes, methods, and modeling techniques for eliciting, analyzing, and specifying software system requirements.
-
A.
The Unified Modeling Language Reference Manual
The Unified Modeling Language Reference Manual is a comprehensive technical guide that defines and explains the UML standard for modeling software and systems.
-
B.
Object-Oriented Software Engineering: A Use Case Driven Approach
Object-Oriented Software Engineering: A Use Case Driven Approach is a foundational software engineering textbook by Ivar Jacobson that popularized use-case–driven, object-oriented analysis and design methods.
-
C.
Object-Oriented Analysis and Design with Applications
Object-Oriented Analysis and Design with Applications is a foundational software engineering book by Grady Booch that systematically presents object-oriented concepts, methods, and practical design techniques.
-
D.
Essence: The Software Engineering Method
"Essence: The Software Engineering Method" is a framework introduced by Ivar Jacobson that defines a common, lightweight kernel and language for describing and improving software engineering practices.
-
E.
A Discipline for Software Engineering
"A Discipline for Software Engineering" is a book by Watts S. Humphrey that introduces and explains the Personal Software Process (PSP), a structured methodology for individual software engineers to improve the quality and predictability of their work.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0cec448190b30466628a2ff23f |
completed | April 18, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0148435f6081909bfc6cc1ef59d971 |
completed | May 11, 2026, 3:08 a.m. |
| NEDg | Description generation | batch_6a014a4fdcf081908be68b1eda2066df |
completed | May 11, 2026, 3:17 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a014adf25808190ad712fbd7560e91d |
completed | May 11, 2026, 3:19 a.m. |
Created at: April 10, 2026, 5:37 a.m.