Triple
T13019590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TComboBox |
E322638
|
entity |
| Predicate | supportsTabOrder |
P107476
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [TComboBox, supportsTabOrder, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTabOrder Context triple: [TComboBox, supportsTabOrder, true]
-
A.
supportsOrderAttribute
Indicates that one entity is capable of handling, recognizing, or providing a specified attribute associated with an order.
-
B.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
-
C.
supportsKeyboard
Indicates that one entity is compatible with or able to be operated using a keyboard as an input method.
-
D.
mayProvideFocus
Indicates that one entity can potentially direct attention, emphasis, or concentration toward another entity or aspect.
-
E.
supportsControllerInput
Indicates that an entity is capable of receiving and handling input from a controller device.
- F. None of above. chosen
Provenance (4 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecf21bc819082fb512bc479b4be |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:51 p.m.