Triple
T30421933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM Gekko |
E773922
|
entity |
| Predicate | mainCPUOf |
P114053
|
FINISHED |
| Object | Nintendo GameCube |
—
|
NE NERFINISHED |
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: Nintendo GameCube | Statement: [IBM Gekko, mainCPUOf, Nintendo GameCube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCPUOf Context triple: [IBM Gekko, mainCPUOf, Nintendo GameCube]
-
A.
primaryCpu
chosen
Indicates that one CPU is designated as the main or primary processing unit in relation to another component or system.
-
B.
cpu
Indicates that an entity functions as, contains, or is associated with a central processing unit (CPU) in a computational system.
-
C.
secondaryCpu
Indicates that one CPU functions as a secondary or backup processor in relation to a primary CPU.
-
D.
typicalCPU
Indicates that an entity uses or is associated with a standard or commonly used CPU for its type or category.
-
E.
hasCPUCore
Indicates that an entity (typically a computing device or processor) possesses or includes a specific CPU core as one of its components.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 8:06 p.m.