Triple
T24928878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adobe Dynamic Link |
E618933
|
entity |
| Predicate | workflowType |
P26991
|
FINISHED |
| Object | non-destructive workflow |
—
|
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: non-destructive workflow | Statement: [Adobe Dynamic Link, workflowType, non-destructive workflow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workflowType Context triple: [Adobe Dynamic Link, workflowType, non-destructive workflow]
-
A.
typicalWorkflow
chosen
Indicates that one process, sequence, or set of actions represents the standard or commonly followed way of performing a task or achieving a goal.
-
B.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
C.
workTypeOfSetting
Indicates the type or nature of work activity that characterizes or occurs within a particular setting.
-
D.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
E.
workModel
Indicates that one entity serves as, or is based on, a particular model used for work, operation, or functional behavior.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:29 a.m.