Triple
T6525528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DEKA Arm System |
E151291
|
entity |
| Predicate | intendedUserGroup |
P17010
|
FINISHED |
| Object | military veterans with upper-limb loss |
—
|
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: military veterans with upper-limb loss | Statement: [DEKA Arm System, intendedUserGroup, military veterans with upper-limb loss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedUserGroup Context triple: [DEKA Arm System, intendedUserGroup, military veterans with upper-limb loss]
-
A.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
-
B.
usedByGroup
Indicates that something is utilized or employed by a particular group or collective entity.
-
C.
accessibleForGroups
Indicates that something can be accessed or used by one or more specified groups.
-
D.
primaryUserGroup
chosen
Indicates the main or default user group to which a user is primarily assigned or associated.
-
E.
participantGroup
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ada77b448190b6e0e07494fb4dd3 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.