Triple
T22443716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESLint |
E554816
|
entity |
| Predicate | maintainer |
P2962
|
FINISHED |
| Object | ESLint team |
—
|
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: ESLint team | Statement: [ESLint, maintainer, ESLint team]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ESLint team Context triple: [ESLint, maintainer, ESLint team]
-
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.
Babel core team
The Babel core team is the group of developers responsible for designing, implementing, and maintaining the Babel JavaScript compiler and its ecosystem.
-
C.
Svelte core team
The Svelte core team is the group of developers responsible for designing, maintaining, and advancing the Svelte framework and its official tooling.
-
D.
Microsoft TypeScript team
The Microsoft TypeScript team is the group at Microsoft responsible for designing, developing, and maintaining the TypeScript programming language and its ecosystem.
-
E.
Vue.js core team
The Vue.js core team is the group of primary developers and maintainers responsible for designing, implementing, and evolving the Vue.js framework and its official ecosystem tools.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae40f9081908674015beb33f74e |
completed | April 29, 2026, 1:12 a.m. |
Created at: April 16, 2026, 8:47 p.m.