Triple
T33316589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCKSimpleTaskViewController |
E853031
|
entity |
| Predicate | typicalTaskType |
P107993
|
FINISHED |
| Object | simple check task |
—
|
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: simple check task | Statement: [OCKSimpleTaskViewController, typicalTaskType, simple check task]
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 (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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:33 a.m.