Triple

T19508983
Position Surface form Disambiguated ID Type / Status
Subject Java EE 6 E488097 entity
Predicate followedBy P78 FINISHED
Object Java EE 7 — NE NERFINISHED

How this triple was built (3 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 7 | Statement: [Java EE 6, followedBy, Java EE 7]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Java EE 7
Context triple: [Java EE 6, followedBy, Java EE 7]
  • A. Java EE 6
    Java EE 6 is a version of the Java Platform, Enterprise Edition that standardizes APIs and services for building and deploying enterprise-level, web-based, and distributed applications in Java.
  • B. Jakarta EE
    Jakarta EE is a set of specifications that extend the Java SE platform for enterprise-level applications, defining standard APIs for building scalable, secure, and portable Java-based enterprise software.
  • C. Java EE 5
    Java EE 5 is a major version of the Java Platform, Enterprise Edition that introduced simplified enterprise development features such as annotations, POJO-based programming, and enhanced web services support for building scalable, distributed applications.
  • D. Java EE
    Java EE is a widely used enterprise-grade Java platform specification for building scalable, distributed, and transactional server-side applications.
  • E. Jakarta EE application server
    A Jakarta EE application server is a software platform that provides the runtime environment and services needed to deploy, manage, and execute enterprise Java applications built on the Jakarta EE specifications.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Java EE 7
Target entity description: Java EE 7 is a major version of the Java Platform, Enterprise Edition that enhanced support for HTML5, WebSocket, JSON processing, and simplified enterprise application development through improved APIs and configuration.
  • A. Java EE 6
    Java EE 6 is a version of the Java Platform, Enterprise Edition that standardizes APIs and services for building and deploying enterprise-level, web-based, and distributed applications in Java.
  • B. Jakarta EE
    Jakarta EE is a set of specifications that extend the Java SE platform for enterprise-level applications, defining standard APIs for building scalable, secure, and portable Java-based enterprise software.
  • C. Java EE 5
    Java EE 5 is a major version of the Java Platform, Enterprise Edition that introduced simplified enterprise development features such as annotations, POJO-based programming, and enhanced web services support for building scalable, distributed applications.
  • D. Java EE
    Java EE is a widely used enterprise-grade Java platform specification for building scalable, distributed, and transactional server-side applications.
  • E. Jakarta EE application server
    A Jakarta EE application server is a software platform that provides the runtime environment and services needed to deploy, manage, and execute enterprise Java applications built on the Jakarta EE specifications.
  • F. None of above. chosen

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_69d8e8d9d1c88190b01cd78b8be49384 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6351426448190aec1ee26c09faa24 completed April 20, 2026, 2:15 p.m.
Created at: April 10, 2026, 1:40 p.m.