Triple
T23155491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Marick |
E578424
|
entity |
| Predicate | hasWrittenArticle |
P14097
|
FINISHED |
| Object | Agile Testing Directions |
—
|
NE NERFINISHED |
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: Agile Testing Directions | Statement: [Brian Marick, hasWrittenArticle, Agile Testing Directions]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Agile Testing Directions Context triple: [Brian Marick, hasWrittenArticle, Agile Testing Directions]
-
A.
Exploratory Software Testing
Exploratory Software Testing is a software testing approach that emphasizes simultaneous learning, test design, and execution, relying on tester creativity and adaptability rather than strictly predefined test cases.
-
B.
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.
-
C.
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.
-
D.
Extreme Programming Explained
Extreme Programming Explained is a foundational book by Kent Beck that introduces and details the principles, practices, and philosophy of the Extreme Programming (XP) agile software development methodology.
-
E.
Framework for Integrated Test (FIT)
Framework for Integrated Test (FIT) is an early agile testing framework that lets customers, testers, and developers collaboratively define and automatically execute executable specifications using simple, table-based documents.
- 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: Agile Testing Directions Target entity description: Agile Testing Directions is an influential article by software tester and author Brian Marick that outlines principles and practices for integrating testing into agile software development.
-
A.
Exploratory Software Testing
Exploratory Software Testing is a software testing approach that emphasizes simultaneous learning, test design, and execution, relying on tester creativity and adaptability rather than strictly predefined test cases.
-
B.
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.
-
C.
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.
-
D.
Extreme Programming Explained
Extreme Programming Explained is a foundational book by Kent Beck that introduces and details the principles, practices, and philosophy of the Extreme Programming (XP) agile software development methodology.
-
E.
Framework for Integrated Test (FIT)
Framework for Integrated Test (FIT) is an early agile testing framework that lets customers, testers, and developers collaboratively define and automatically execute executable specifications using simple, table-based documents.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWrittenArticle Context triple: [Brian Marick, hasWrittenArticle, Agile Testing Directions]
-
A.
hasWrittenAbout
chosen
Indicates that one entity has authored content or material discussing, analyzing, or referencing another entity.
-
B.
hasWrittenFor
Indicates that one entity has created written content (such as articles, stories, or texts) for or on behalf of another entity, typically a publication, organization, or platform.
-
C.
hasWrittenNonFiction
Indicates that a person is the author of one or more non-fiction works.
-
D.
hasWrittenWorkType
Indicates that an entity (typically a written work) is associated with a specific type or category of written work (such as novel, article, report, etc.).
-
E.
hasAuthorPublished
Indicates that a specific author has produced and made publicly available at least one work, such as a book, article, or paper.
- F. None of above.
Provenance (3 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. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.