Triple
T33434754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamepad API |
E856214
|
entity |
| Predicate | buttonValuesRange |
P28992
|
FINISHED |
| Object | 0.0 to 1.0 |
—
|
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: 0.0 to 1.0 | Statement: [Gamepad API, buttonValuesRange, 0.0 to 1.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buttonValuesRange Context triple: [Gamepad API, buttonValuesRange, 0.0 to 1.0]
-
A.
controlRange
Indicates the spatial or contextual extent within which an entity can exert control or influence over another entity or process.
-
B.
testRange
Indicates that a value, condition, or behavior is being evaluated to determine whether it falls within a specified range or interval.
-
C.
rangeOf
chosen
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
D.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
E.
controlCodeRange
Indicates that one entity specifies or constrains the allowable range of control codes applicable to 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e483f0f48190b38bbb7d0d335c2e |
completed | May 3, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.