Triple

T9097261
Position Surface form Disambiguated ID Type / Status
Subject KDE Applications E218058 entity
Predicate uses P98 FINISHED
Object Qt E206057 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: Qt | Statement: [KDE Applications, uses, Qt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Qt
Context triple: [KDE Applications, uses, Qt]
  • A. Qt chosen
    Qt is a cross-platform application development framework widely used for building graphical user interfaces and multi-platform software in C++.
  • B. QML
    QML is a declarative language used in the Qt framework to design fluid, dynamic user interfaces, particularly for mobile and embedded applications.
  • C. KDE Frameworks
    KDE Frameworks is a collection of modular, reusable libraries and software components that provide core functionality and services for building KDE and Qt-based applications.
  • D. Qt Jambi
    Qt Jambi is a set of Java bindings for the Qt application framework, enabling developers to build cross-platform GUI and non-GUI applications in Java using Qt’s features.
  • E. QtWebKit
    QtWebKit is a port of the WebKit browser engine that integrates it with the Qt application framework for embedding web content in Qt-based 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_69ca83d9844081908e561e367fda6d45 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc96b7d0d48190a3b15f35bef087e3 completed April 1, 2026, 3:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69d054455e10819095738caf0d5795e2 completed April 3, 2026, 11:59 p.m.
Created at: March 30, 2026, 7:15 p.m.