Triple
T36166644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Coates |
E1046019
|
entity |
| Predicate | taskDescription |
P107993
|
FINISHED |
| Object | drives cattle to market |
—
|
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: drives cattle to market | Statement: [Mr. Coates, taskDescription, drives cattle to market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskDescription Context triple: [Mr. Coates, taskDescription, drives cattle to market]
-
A.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
B.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
-
C.
taskName
Indicates the specific name or label assigned to a task within a process or workflow.
-
D.
goalDescription
Indicates that an entity expresses, specifies, or provides a textual description of a goal or intended outcome associated with another entity or activity.
-
E.
typicalTask
chosen
Indicates the kind of task or activity that is normally or characteristically performed by an entity.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.