Triple
T22443967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebdriverIO |
E554819
|
entity |
| Predicate | supportsAssertionStyle |
P25603
|
FINISHED |
| Object | BDD |
—
|
LITERAL 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: BDD | Statement: [WebdriverIO, supportsAssertionStyle, BDD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAssertionStyle Context triple: [WebdriverIO, supportsAssertionStyle, BDD]
-
A.
supportsAssertionLibraries
chosen
Indicates that one entity provides compatibility with or functionality for using specific assertion libraries in conjunction with another entity.
-
B.
typicalAssertionLibrary
Indicates that one entity is a standard or commonly used collection of assertions or checks applied within the context of another entity (such as a test, framework, or system).
-
C.
assertedIn
Indicates that a statement, claim, or relation is explicitly made or declared within a particular source, context, or document.
-
D.
conformanceStyle
Indicates the specific manner, pattern, or set of rules by which something adheres to or complies with a given standard or specification.
-
E.
assertedViolationOf
Indicates that one party has formally claimed or alleged that a rule, law, standard, or obligation has been violated.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae517208190924a7968723f55ef |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.