Triple

T22489091
Position Surface form Disambiguated ID Type / Status
Subject BDD E555967 entity
Predicate relatedTo P37 FINISHED
Object Specification by Example — 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: Specification by Example | Statement: [BDD, relatedTo, Specification by Example]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Specification by Example
Context triple: [BDD, relatedTo, Specification by Example]
  • A. 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.
  • B. Concordion
    Concordion is a specification-by-example testing framework for Java that lets you write executable acceptance tests in plain English within HTML documents.
  • C. BDD
    BDD (Behavior-Driven Development) is a software development approach that emphasizes collaboration between developers, testers, and business stakeholders by defining system behavior through human-readable, example-based specifications.
  • D. RSpec Story Runner (early BDD tools)
    RSpec Story Runner was an early behavior-driven development tool for Ruby that introduced a narrative, story-based style of specifying application behavior before it evolved into RSpec’s more familiar example-based syntax.
  • E. 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.
  • 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: Specification by Example
Target entity description: Specification by Example is a collaborative, example-driven approach to defining software requirements and acceptance tests that underpins many behavior-driven development practices.
  • A. 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.
  • B. Concordion
    Concordion is a specification-by-example testing framework for Java that lets you write executable acceptance tests in plain English within HTML documents.
  • C. BDD chosen
    BDD (Behavior-Driven Development) is a software development approach that emphasizes collaboration between developers, testers, and business stakeholders by defining system behavior through human-readable, example-based specifications.
  • D. RSpec Story Runner (early BDD tools)
    RSpec Story Runner was an early behavior-driven development tool for Ruby that introduced a narrative, story-based style of specifying application behavior before it evolved into RSpec’s more familiar example-based syntax.
  • E. 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.
  • 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_69e11e53897c819088863779f8c50bb0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15c3f3b4c819092bfe6495c61db46 completed April 29, 2026, 1:17 a.m.
Created at: April 16, 2026, 8:49 p.m.