Triple
T23155390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disciplined Agile Delivery |
E578422
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Disciplined Agile toolkit |
—
|
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: Disciplined Agile toolkit | Statement: [Disciplined Agile Delivery, partOf, Disciplined Agile toolkit]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Disciplined Agile toolkit Context triple: [Disciplined Agile Delivery, partOf, Disciplined Agile toolkit]
-
A.
Disciplined Agile Delivery
Disciplined Agile Delivery is a process decision framework that extends and refines agile and lean approaches to provide pragmatic, context-sensitive guidance for end-to-end software delivery in enterprises.
-
B.
Scaled Agile Framework
Scaled Agile Framework is a structured methodology for applying agile and lean principles at enterprise scale to coordinate multiple teams and large, complex development efforts.
-
C.
Agile Software Development, Principles, Patterns, and Practices
"Agile Software Development, Principles, Patterns, and Practices" is a foundational software engineering book by Robert C. Martin that explains agile methodologies through object-oriented design principles, design patterns, and best practices for building maintainable code.
-
D.
Clean Agile: Back to Basics
Clean Agile: Back to Basics is a book by Robert C. Martin that revisits and clarifies the core principles and practices of Agile software development.
-
E.
Agile Manifesto
The Agile Manifesto is a foundational document in software development that outlines core values and principles favoring collaboration, adaptability, and customer-focused iterative delivery over rigid processes and extensive documentation.
- 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: Disciplined Agile toolkit Target entity description: The Disciplined Agile toolkit is a process decision framework that guides organizations in choosing and evolving agile and lean ways of working across the enterprise.
-
A.
Disciplined Agile Delivery
chosen
Disciplined Agile Delivery is a process decision framework that extends and refines agile and lean approaches to provide pragmatic, context-sensitive guidance for end-to-end software delivery in enterprises.
-
B.
Scaled Agile Framework
Scaled Agile Framework is a structured methodology for applying agile and lean principles at enterprise scale to coordinate multiple teams and large, complex development efforts.
-
C.
Agile Software Development, Principles, Patterns, and Practices
"Agile Software Development, Principles, Patterns, and Practices" is a foundational software engineering book by Robert C. Martin that explains agile methodologies through object-oriented design principles, design patterns, and best practices for building maintainable code.
-
D.
Clean Agile: Back to Basics
Clean Agile: Back to Basics is a book by Robert C. Martin that revisits and clarifies the core principles and practices of Agile software development.
-
E.
Agile Manifesto
The Agile Manifesto is a foundational document in software development that outlines core values and principles favoring collaboration, adaptability, and customer-focused iterative delivery over rigid processes and extensive documentation.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efca1f081908ff1c34ba25f40c3 |
completed | April 29, 2026, 4:54 a.m. |
Created at: April 17, 2026, 4:01 p.m.