Triple
T33316589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCKSimpleTaskViewController |
E853031
|
entity |
| Predicate | typicalTaskType |
—
|
GENERATED |
| Object | simple check task |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTaskType Context triple: [OCKSimpleTaskViewController, typicalTaskType, simple check task]
-
A.
typicalTask
chosen
Indicates the kind of task or activity that is normally or characteristically performed by an entity.
-
B.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
C.
typicalWorkflow
Indicates that one process, sequence, or set of actions represents the standard or commonly followed way of performing a task or achieving a goal.
-
D.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
-
E.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
- F. None of above.
Provenance (1 batch)
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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:33 a.m.