Triple

T11656636
Position Surface form Disambiguated ID Type / Status
Subject JDK 1.1 E277025 entity
Predicate notableChangeFromPreviousVersion P13888 FINISHED
Object introduction of inner classes 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: introduction of inner classes | Statement: [JDK 1.1, notableChangeFromPreviousVersion, introduction of inner classes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableChangeFromPreviousVersion
Context triple: [JDK 1.1, notableChangeFromPreviousVersion, introduction of inner classes]
  • A. notableChange chosen
    Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
  • B. notableRuleChange
    Indicates a significant modification to an established rule or set of rules that meaningfully alters how they apply or are enforced.
  • C. notableVersionType
    Indicates that one version of an entity is recognized as particularly significant or noteworthy relative to other versions.
  • D. notableMigration
    Indicates a significant movement or relocation of people, animals, or entities from one place to another, notable for its scale, impact, or historical importance.
  • E. notableRelease
    Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
  • 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_69d6aafbb3c081908a9cdb4ecb8d981d completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a3d0331481909682b2e504e4c9a0 completed April 10, 2026, 7:16 a.m.
PD Predicate disambiguation batch_69d85ddc780481909a3bc63832fe2bd2 completed April 10, 2026, 2:18 a.m.
Created at: April 8, 2026, 9:39 p.m.