Triple
T22443761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESLint |
E554816
|
entity |
| Predicate | supportsRuleSeverity |
P148216
|
FINISHED |
| Object | error |
—
|
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: error | Statement: [ESLint, supportsRuleSeverity, error]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRuleSeverity Context triple: [ESLint, supportsRuleSeverity, error]
-
A.
supportsRuleType
Indicates that one entity is capable of handling, applying, or being compatible with a specified type of rule.
-
B.
hasRule
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
C.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
D.
enforcesRule
Indicates that one entity compels or ensures that another entity follows or complies with a specified rule or set of rules.
-
E.
supportRules
Indicates that one entity provides justification, backing, or validation for the rules or constraints defined by another entity.
- F. None of above. chosen
Provenance (4 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. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.