Triple
T17175614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axel van Lamsweerde |
E416850
|
entity |
| Predicate | knownFor |
P22
|
FINISHED |
| Object |
KAOS requirements engineering framework
The KAOS requirements engineering framework is a goal-oriented methodology for systematically capturing, analyzing, and refining software system requirements into precise, formal specifications.
|
E1254561
|
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: KAOS requirements engineering framework | Statement: [Axel van Lamsweerde, knownFor, KAOS requirements engineering framework]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KAOS requirements engineering framework Context triple: [Axel van Lamsweerde, knownFor, KAOS requirements engineering framework]
-
A.
ATAM (Architecture Tradeoff Analysis Method)
ATAM (Architecture Tradeoff Analysis Method) is a structured software architecture evaluation approach that helps stakeholders analyze and compare quality attribute trade-offs and risks in complex systems.
-
B.
Software & Systems Process Engineering Metamodel
The Software & Systems Process Engineering Metamodel (SPEM) is an OMG standard modeling language used to define, document, and manage software and systems development processes.
-
C.
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.
-
D.
Rational Unified Process
Rational Unified Process is an iterative, use-case–driven software development framework created by Rational Software to provide structured guidance across the full lifecycle of object-oriented projects.
-
E.
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.
- 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: KAOS requirements engineering framework Triple: [Axel van Lamsweerde, knownFor, KAOS requirements engineering framework]
Generated description
The KAOS requirements engineering framework is a goal-oriented methodology for systematically capturing, analyzing, and refining software system requirements into precise, formal specifications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: KAOS requirements engineering framework Target entity description: The KAOS requirements engineering framework is a goal-oriented methodology for systematically capturing, analyzing, and refining software system requirements into precise, formal specifications.
-
A.
ATAM (Architecture Tradeoff Analysis Method)
ATAM (Architecture Tradeoff Analysis Method) is a structured software architecture evaluation approach that helps stakeholders analyze and compare quality attribute trade-offs and risks in complex systems.
-
B.
Software & Systems Process Engineering Metamodel
The Software & Systems Process Engineering Metamodel (SPEM) is an OMG standard modeling language used to define, document, and manage software and systems development processes.
-
C.
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.
-
D.
Rational Unified Process
Rational Unified Process is an iterative, use-case–driven software development framework created by Rational Software to provide structured guidance across the full lifecycle of object-oriented projects.
-
E.
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.
- 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.