Triple

T8806566
Position Surface form Disambiguated ID Type / Status
Subject Inprise Corporation E209546 entity
Predicate product P490 FINISHED
Object InterBase E302985 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: InterBase | Statement: [Inprise Corporation, product, InterBase]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: InterBase
Context triple: [Inprise Corporation, product, InterBase]
  • A. InterBase chosen
    InterBase is a lightweight, cross-platform relational database management system known for its small footprint, embedded deployment capabilities, and support for SQL-based applications.
  • B. Sybase
    Sybase is a pioneering enterprise software company best known for its relational database management systems and data management solutions, later acquired by SAP.
  • C. dBASE
    dBASE is one of the earliest and most influential database management systems for microcomputers, widely used in the 1980s for business and application development.
  • D. SAP MaxDB
    SAP MaxDB is a relational database management system developed by SAP, commonly used for enterprise applications and SAP solutions.
  • E. Actian
    Actian is a data management and analytics company known for its hybrid data platforms and database technologies used in enterprise applications.
  • 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_69ca836320e48190b5cf585b90a322c4 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5fd1f1a08190a2e584f6b0495f5c completed March 31, 2026, 11:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf6f96bb448190b9316ad55d61662a completed April 3, 2026, 7:43 a.m.
Created at: March 30, 2026, 6:45 p.m.