Triple
T10427472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberty BASIC |
E245822
|
entity |
| Predicate | supportsGUI |
P84825
|
FINISHED |
| Object | Windows graphical user interface |
—
|
LITERAL 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: Windows graphical user interface | Statement: [Liberty BASIC, supportsGUI, Windows graphical user interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGUI Context triple: [Liberty BASIC, supportsGUI, Windows graphical user interface]
-
A.
supportsGraphicalUserInterface
chosen
Indicates that an entity is capable of operating with or providing a graphical user interface for interaction.
-
B.
usesGUIFramework
Indicates that one entity employs or is built upon a particular graphical user interface (GUI) framework to provide its visual or interactive functionality.
-
C.
supportsView
Indicates that one entity provides the capability to display, render, or present another entity in a particular view or format.
-
D.
supportsCommand
Indicates that one entity is capable of recognizing, accepting, or executing a specified command associated with another entity.
-
E.
supportsGraphicsSwitching
Indicates that an entity can dynamically switch between different graphics hardware or rendering modes, typically to balance performance and power usage.
- F. None of above.
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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea4a7dcc81909a830e08656a1c0c |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:12 p.m.