Triple

T11656502
Position Surface form Disambiguated ID Type / Status
Subject DriverManager E277023 entity
Predicate fullyQualifiedName P79141 FINISHED
Object java.sql.DriverManager E277023 NE FINISHED

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.sql.DriverManager | Statement: [DriverManager, fullyQualifiedName, java.sql.DriverManager]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: java.sql.DriverManager
Context triple: [DriverManager, fullyQualifiedName, java.sql.DriverManager]
  • A. DriverManager chosen
    DriverManager is a core JDBC utility class in Java that manages a list of database drivers and establishes connections to databases based on provided URLs and credentials.
  • B. java.sql
    java.sql is a core Java SE package that provides the standard APIs for accessing and manipulating relational databases using SQL.
  • C. JDBC
    JDBC (Java Database Connectivity) is a Java-based API that enables applications to connect to and interact with relational databases in a standardized way.
  • 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. ODBC Driver Manager
    ODBC Driver Manager is a software component that coordinates communication between applications using ODBC and the appropriate database-specific ODBC drivers.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fullyQualifiedName
Context triple: [DriverManager, fullyQualifiedName, java.sql.DriverManager]
  • A. hasFullNameReference chosen
    Indicates that one entity serves as a complete, explicit name or designation referring to another entity.
  • B. complexName
    Indicates that an entity has a multi-part or structurally intricate name, typically composed of several elements or components.
  • C. typicalFullName
    Indicates that the object is the standard or commonly used full name associated with the subject.
  • D. fullCaseName
    Indicates that one entity is the complete, formal name of a legal case associated with another entity.
  • E. commonNameOf
    Indicates that one entity is the commonly used or popular name by which the other entity is known.
  • F. None of above.

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_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.
PD Predicate disambiguation batch_69d85ddc780481909a3bc63832fe2bd2 completed April 10, 2026, 2:18 a.m.
Created at: April 8, 2026, 9:39 p.m.