Triple

T18799721
Position Surface form Disambiguated ID Type / Status
Subject PyQt5 E459729 entity
Predicate implements P1417 FINISHED
Object Qt Core API NE NERFINISHED

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 Core API | Statement: [PyQt5, implements, Qt Core API]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Qt Core API
Context triple: [PyQt5, implements, Qt Core API]
  • 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. KDeclarative
    KDeclarative is a KDE Frameworks library that integrates Qt Quick/QML with KDE technologies to simplify building declarative user interfaces.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8d398c7d4819091cb2f7e48948aeb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5a02273b481909bc250144a0ace32 completed April 20, 2026, 3:40 a.m.
Created at: April 10, 2026, 11:53 a.m.