Triple
T6961730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adobe Character Animator |
E161384
|
entity |
| Predicate | usesInputDevice |
P9919
|
FINISHED |
| Object | webcam |
—
|
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: webcam | Statement: [Adobe Character Animator, usesInputDevice, webcam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInputDevice Context triple: [Adobe Character Animator, usesInputDevice, webcam]
-
A.
inputDevice
Indicates that one entity functions as a device used to provide input to another entity or system.
-
B.
usesDevice
chosen
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
C.
supportsUserInteraction
Indicates that an entity enables or facilitates direct interaction with a user, such as receiving input or providing responsive feedback.
-
D.
hasInput
Indicates that an entity receives or takes another entity as an input to its process, function, or operation.
-
E.
usesSoundDevice
Indicates that one entity operates or relies on a sound-producing or sound-processing device in relation to another entity or context.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daf07e3481909aa79b8e0f1b1be7 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.