Triple
T8806758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCL |
E209550
|
entity |
| Predicate | widgetset |
P84716
|
FINISHED |
| Object | fpGUI |
E209552
|
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: fpGUI | Statement: [LCL, widgetset, fpGUI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: fpGUI Context triple: [LCL, widgetset, fpGUI]
-
A.
fpGUI
chosen
fpGUI is a cross-platform, object-oriented GUI toolkit for Free Pascal that provides a lightweight alternative to other widget sets for building native-looking desktop applications.
-
B.
Gui
Gui is a short form or nickname commonly used for the given name Guillaume.
-
C.
Plastic GUI
Plastic GUI is the graphical user interface client for the Plastic SCM version control system, providing visual tools for managing source code and repository operations.
-
D.
Gluon GUI
Gluon GUI is a graphical user interface client for Plastic SCM that provides an easy, visual way to manage version control tasks.
-
E.
Presentation Manager GUI
Presentation Manager GUI is the graphical user interface subsystem of IBM's OS/2 operating system, providing windows, menus, and desktop interaction for 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.