Triple
T22443976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebdriverIO |
E554819
|
entity |
| Predicate | supportsSelectorStrategy |
P13064
|
FINISHED |
| Object | CSS selectors |
—
|
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: CSS selectors | Statement: [WebdriverIO, supportsSelectorStrategy, CSS selectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSelectorStrategy Context triple: [WebdriverIO, supportsSelectorStrategy, CSS selectors]
-
A.
hasSelector
Indicates that one entity specifies or identifies a particular part, segment, or subset of another entity through a selection mechanism.
-
B.
usesStrategy
chosen
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
C.
hasSelectionStandard
Indicates that there is a defined criterion or set of rules used to choose or filter items, options, or entities.
-
D.
hasSelectionFor
Indicates that one entity holds or specifies a chosen option, subset, or configuration on behalf of another entity.
-
E.
hasAdaptationStrategy
Indicates that an entity employs or is associated with a specific method or approach for adapting to changing conditions or requirements.
- 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.