Triple
T19436748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rational Software |
E486242
|
entity |
| Predicate | product |
P490
|
FINISHED |
| Object | Rational RequisitePro |
—
|
NE NERFINISHED |
How this triple was built (3 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: Rational RequisitePro | Statement: [Rational Software, product, Rational RequisitePro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rational RequisitePro Context triple: [Rational Software, product, Rational RequisitePro]
-
A.
Rational software tools
Rational software tools are a suite of IBM-developed software engineering products that support tasks such as requirements management, modeling, design, testing, and project management across the software development lifecycle.
-
B.
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.
-
C.
IBM Rational Requirements Composer
IBM Rational Requirements Composer is a collaborative requirements definition and management tool from IBM that supports capturing, analyzing, and tracking software and systems requirements throughout the development lifecycle.
-
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.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Rational RequisitePro Target entity description: Rational RequisitePro is a requirements management tool that integrates with Microsoft Word to help software development teams capture, organize, and trace project requirements.
-
A.
Rational software tools
chosen
Rational software tools are a suite of IBM-developed software engineering products that support tasks such as requirements management, modeling, design, testing, and project management across the software development lifecycle.
-
B.
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.
-
C.
IBM Rational Requirements Composer
IBM Rational Requirements Composer is a collaborative requirements definition and management tool from IBM that supports capturing, analyzing, and tracking software and systems requirements throughout the development lifecycle.
-
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.
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.
- F. None of above.
Provenance (2 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633618c2881908f3d2a9cabb02289 |
completed | April 20, 2026, 2:08 p.m. |
Created at: April 10, 2026, 1:38 p.m.