Triple
T29900852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TButton |
E759402
|
entity |
| Predicate | hasFocusBehavior |
P189344
|
FINISHED |
| Object | can receive keyboard focus |
—
|
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: can receive keyboard focus | Statement: [TButton, hasFocusBehavior, can receive keyboard focus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFocusBehavior Context triple: [TButton, hasFocusBehavior, can receive keyboard focus]
-
A.
hasFocusSystem
Indicates that one entity is the primary system or subsystem that another entity is currently directing its attention, control, or processing resources toward.
-
B.
hasFocusText
Indicates that one entity provides the primary or highlighted textual content associated with another entity.
-
C.
hasFocusMethod
Indicates that an entity employs a particular method or approach to direct or manage focus or attention.
-
D.
haveFocusSystem
Indicates that an entity is currently the primary target or active focus within a system or context.
-
E.
hasFocusGroup
Indicates that an entity is associated with or participates in a specific focus group for targeted discussion, feedback, or research.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: April 29, 2026, 6:06 p.m.