Triple

T11656607
Position Surface form Disambiguated ID Type / Status
Subject JDK 1.1 E277025 entity
Predicate introducesAPI P31856 FINISHED
Object JDBC 1.0 E56740 NE 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: JDBC 1.0 | Statement: [JDK 1.1, introducesAPI, JDBC 1.0]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: JDBC 1.0
Context triple: [JDK 1.1, introducesAPI, JDBC 1.0]
  • A. JDBC chosen
    JDBC (Java Database Connectivity) is a Java-based API that enables applications to connect to and interact with relational databases in a standardized way.
  • B. JDK 1.0
    JDK 1.0 was the first official release of the Java Development Kit, marking the initial public launch of the Java Platform, Standard Edition for building and running Java applications.
  • C. java.sql
    java.sql is a core Java SE package that provides the standard APIs for accessing and manipulating relational databases using SQL.
  • D. javax.sql
    javax.sql is a Java package that provides extended JDBC support for database access, including connection pooling, distributed transactions, and rowset implementations.
  • E. JDK 1.1
    JDK 1.1 is an early major release of the Java Development Kit that significantly expanded the Java platform with features like inner classes, JavaBeans, reflection, and improved library support.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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.
NED1 Entity disambiguation (via context triple) batch_69ee88166900819095063f045be44bed completed April 26, 2026, 9:48 p.m.
Created at: April 8, 2026, 9:39 p.m.