Triple
T20003370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple M8 motion coprocessor |
E494389
|
entity |
| Predicate | offloadsWorkFrom |
P99809
|
FINISHED |
| Object | main CPU |
—
|
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: main CPU | Statement: [Apple M8 motion coprocessor, offloadsWorkFrom, main CPU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offloadsWorkFrom Context triple: [Apple M8 motion coprocessor, offloadsWorkFrom, main CPU]
-
A.
offloadsFrom
chosen
Indicates that a task, responsibility, or load is transferred or shifted away from one entity to another.
-
B.
offloadingMethod
Indicates the method or process by which something is transferred or offloaded from one entity, system, or location to another.
-
C.
spinOffWork
Indicates that one work is derived from, based on, or created as a spin-off of another preexisting work.
-
D.
performsWorkOf
Indicates that one entity carries out, executes, or fulfills the tasks, functions, or role that are normally associated with another entity.
-
E.
performsWork
Indicates that one entity carries out, executes, or engages in work or tasks for or on behalf of another entity or context.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a3ad148190918f9dce755fe470 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.