Triple
T13091255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAPTCHA |
E310467
|
entity |
| Predicate | typicalTask |
P107993
|
FINISHED |
| Object | recognizing distorted text |
—
|
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: recognizing distorted text | Statement: [CAPTCHA, typicalTask, recognizing distorted text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTask Context triple: [CAPTCHA, typicalTask, recognizing distorted text]
-
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.
canTask
Indicates that an entity has the ability or permission to perform a specified task.
-
D.
taskInPlot
Indicates that a specific task occurs within, is associated with, or is part of a particular plot or storyline.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813acbac8190b2fe5e07287457cf |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:03 p.m.