Triple

T32708351
Position Surface form Disambiguated ID Type / Status
Subject JPQL E836332 entity
Predicate previouslyStandardizedIn P198083 FINISHED
Object Java EE 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: Java EE | Statement: [JPQL, previouslyStandardizedIn, Java EE]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: previouslyStandardizedIn
Context triple: [JPQL, previouslyStandardizedIn, Java EE]
  • A. previouslyStandardizedBy
    Indicates that an entity was standardized or formally defined by another entity at some earlier time, but that standardization is no longer current.
  • B. previouslyStandardizedAs
    Indicates that an entity was formerly standardized under a different name, code, or specification than the one it currently has.
  • C. standardizedIn
    Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
  • D. standardizedBy
    Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
  • E. isStandardizedAcross
    Indicates that something maintains a consistent, uniform form, method, or specification across multiple instances, contexts, or locations.
  • 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_69f3493446148190819541f3ffe79975 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fec8aef1d8819094c7fd7074038e6b completed May 9, 2026, 5:39 a.m.
PD Predicate disambiguation batch_69fec639876481908efd84a3631a4271 completed May 9, 2026, 5:29 a.m.
PDg Predicate description generation batch_69fec8adaa308190a9a276f8c36f15f0 completed May 9, 2026, 5:39 a.m.
Created at: May 1, 2026, 1:10 a.m.