Triple
T29247130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buriki One |
E741469
|
entity |
| Predicate | controlSchemeFeature |
P98668
|
FINISHED |
| Object | buttons used for movement |
—
|
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: buttons used for movement | Statement: [Buriki One, controlSchemeFeature, buttons used for movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlSchemeFeature Context triple: [Buriki One, controlSchemeFeature, buttons used for movement]
-
A.
hasControlScheme
chosen
Indicates that one entity defines or uses a particular control scheme or input configuration associated with another entity.
-
B.
controlFeatures
Indicates that one entity has the ability to configure, manage, or influence the operational settings or characteristics of another entity.
-
C.
controlsFeaturesAt
Indicates that one entity has the authority or capability to manage, configure, or influence specific features at a particular location or context.
-
D.
keyboardFeature
Indicates that one entity is a feature, characteristic, or functional attribute of a keyboard.
-
E.
controlsType
Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of another entity.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 28, 2026, 12:33 p.m.