Triple
T14394533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebStorm |
E356921
|
entity |
| Predicate | supportsTechnology |
P5090
|
FINISHED |
| Object | ESLint |
E554816
|
NE 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: ESLint | Statement: [WebStorm, supportsTechnology, ESLint]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ESLint Context triple: [WebStorm, supportsTechnology, ESLint]
-
A.
ESLint
chosen
ESLint is a widely used open-source JavaScript linter that analyzes code to find and fix problems, enforce style rules, and maintain code quality.
-
B.
JSLint
JSLint is a JavaScript code quality and static analysis tool created by Douglas Crockford to enforce strict coding conventions and detect potential errors.
-
C.
Clang-Tidy
Clang-Tidy is a C++ “linter” and static analysis tool that automatically detects and suggests fixes for common programming errors, style issues, and potential bugs in code.
-
D.
Static Code Checker
Static Code Checker is a software tool that automatically analyzes source code without executing it to detect bugs, security vulnerabilities, and style or quality issues.
-
E.
Clang-Tidy linter
Clang-Tidy linter is a C++ code analysis tool that automatically detects and suggests fixes for style issues, bugs, and performance problems using Clang’s compiler infrastructure.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de902d114881908a8f3c01b3c6d309 |
completed | April 14, 2026, 7:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd551b006c8190b84449f2e2b59b62 |
completed | May 8, 2026, 3:14 a.m. |
Created at: April 10, 2026, 1:16 a.m.