Triple
T22443974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebdriverIO |
E554819
|
entity |
| Predicate | supportsExecutionMode |
P99857
|
FINISHED |
| Object | sync mode (legacy) |
—
|
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: sync mode (legacy) | Statement: [WebdriverIO, supportsExecutionMode, sync mode (legacy)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsExecutionMode Context triple: [WebdriverIO, supportsExecutionMode, sync mode (legacy)]
-
A.
supportedMode
chosen
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
B.
supportsSupervisorUserModes
Indicates that an entity provides or enables both supervisor (privileged) and user (unprivileged) operating modes.
-
C.
supportsReferenceModes
Indicates that an entity provides or is compatible with specific reference modes for identifying or accessing other entities.
-
D.
hasCompatibilityMode
Indicates that one entity operates under a special mode or setting designed to maintain compatibility with another entity or with an earlier version.
-
E.
previousExecutionMethodSupported
Indicates that the method used in a prior execution is compatible with or can be used by the current system or process.
- 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.