Triple
T31946198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R1 button |
E815656
|
entity |
| Predicate | isPrimaryShoulderButton |
P62735
|
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: [R1 button, isPrimaryShoulderButton, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryShoulderButton Context triple: [R1 button, isPrimaryShoulderButton, true]
-
A.
hasShoulderButtons
chosen
Indicates that an object, typically a device or controller, includes buttons positioned on its shoulders or top side edges.
-
B.
isTriggerButton
Indicates that an element functions as a control that initiates or triggers a specific action or event when activated.
-
C.
isPrimary
Indicates that one entity holds the main, leading, or most important role or status in relation to another entity or within a given context.
-
D.
isPrimarySetFor
Indicates that one entity is designated as the main or default set associated with another entity.
-
E.
isShoulderStarOf
Indicates that one entity serves as a prominent but secondary or supporting star or featured performer alongside another, akin to a “shoulder” role next to the main star.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 12:06 a.m.