Triple
T28712777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MediaWiki job queue |
E729870
|
entity |
| Predicate | handlesTaskType |
P68920
|
FINISHED |
| Object | page updates |
—
|
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: page updates | Statement: [MediaWiki job queue, handlesTaskType, page updates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesTaskType Context triple: [MediaWiki job queue, handlesTaskType, page updates]
-
A.
hasTaskType
Indicates that an entity is associated with or classified under a specific type or category of task.
-
B.
handlesOperationType
chosen
Indicates that an entity is responsible for processing or managing a specific type or category of operation.
-
C.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
D.
taskTypesEvaluated
Indicates that specific types or categories of tasks have been examined or assessed.
-
E.
hasHandleType
Indicates that one entity possesses or is characterized by a specific type or style of handle.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 5:49 a.m.