Triple

T5996894
Position Surface form Disambiguated ID Type / Status
Subject James Whittaker (software engineer) E133493 entity
Predicate notableWork P4 FINISHED
Object Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design E560745 NE FINISHED

How this triple was built (2 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: Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design | Statement: [James Whittaker (software engineer), notableWork, Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design
Context triple: [James Whittaker (software engineer), notableWork, Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design]
  • A. Exploratory Software Testing chosen
    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. 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.
  • C. How to Break Software
    "How to Break Software" is a practical software testing book that teaches systematic techniques for finding defects by thinking like an attacker of software systems.
  • D. International Symposium on Software Testing and Analysis
    The International Symposium on Software Testing and Analysis is a leading annual research conference focused on advancing the theory and practice of software testing, analysis, and verification.
  • E. How to Break Web Software
    "How to Break Web Software" is a software testing book that focuses on systematically finding security and reliability flaws in web applications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c00870ddbc81909880fa3864f4f38d completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04e963f3c819082dd755e328ab947 completed March 22, 2026, 8:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1136338088190be26e6393b04e018 completed March 23, 2026, 10:18 a.m.
Created at: March 22, 2026, 4:05 p.m.