Triple

T22489116
Position Surface form Disambiguated ID Type / Status
Subject BDD E555967 entity
Predicate oftenImplementedWith P3697 FINISHED
Object SpecFlow NE NERFINISHED

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: SpecFlow | Statement: [BDD, oftenImplementedWith, SpecFlow]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SpecFlow
Context triple: [BDD, oftenImplementedWith, SpecFlow]
  • A. Concordion
    Concordion is a specification-by-example testing framework for Java that lets you write executable acceptance tests in plain English within HTML documents.
  • B. Behat chosen
    Behat is a behavior-driven development (BDD) framework for PHP that lets developers write human-readable tests describing application behavior.
  • C. Behat
    Behat is a small town in the Saharanpur district of Uttar Pradesh, India, known for its agricultural surroundings and local trade.
  • D. 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.
  • E. Ranorex Studio
    Ranorex Studio is a commercial test automation tool for desktop, web, and mobile applications, known for its GUI-based test creation and support for multiple technologies and platforms.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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.