Triple

T28189061
Position Surface form Disambiguated ID Type / Status
Subject JetBrains IDEs via adapters and plugins E716250 entity
Predicate extensibleBy P165430 FINISHED
Object custom JetBrains plugins 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: custom JetBrains plugins | Statement: [JetBrains IDEs via adapters and plugins, extensibleBy, custom JetBrains plugins]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: extensibleBy
Context triple: [JetBrains IDEs via adapters and plugins, extensibleBy, custom JetBrains plugins]
  • A. extendedBy
    Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of another entity.
  • B. extendsTo
    Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
  • C. extendedIn
    Indicates that one entity continues, prolongs, or expands the scope, duration, or range of another entity.
  • D. extendedFrom
    Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
  • E. extendedOn
    Indicates that one entity continues, prolongs, or expands the duration, scope, or effect of another entity beyond its original limit.
  • 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_69efd6b612f48190a72012b520afbd10 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f659355a208190be2609ffc7a9c427 completed May 2, 2026, 8:06 p.m.
PD Predicate disambiguation batch_69f6575d89788190aca478e4aea05a65 completed May 2, 2026, 7:58 p.m.
PDg Predicate description generation batch_69f65875030881909007c502b7dcc998 completed May 2, 2026, 8:03 p.m.
Created at: April 27, 2026, 10:24 p.m.