Triple
T30504594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .TOS |
E776231
|
entity |
| Predicate | primaryCPU |
P114053
|
FINISHED |
| Object | Motorola 68000 @ 8 MHz (typical Atari ST) |
—
|
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: Motorola 68000 @ 8 MHz (typical Atari ST) | Statement: [.TOS, primaryCPU, Motorola 68000 @ 8 MHz (typical Atari ST)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCPU Context triple: [.TOS, primaryCPU, Motorola 68000 @ 8 MHz (typical Atari ST)]
-
A.
primaryCpu
chosen
Indicates that one CPU is designated as the main or primary processing unit in relation to another component or system.
-
B.
secondaryCpu
Indicates that one CPU functions as a secondary or backup processor in relation to a primary CPU.
-
C.
cpu
Indicates that an entity functions as, contains, or is associated with a central processing unit (CPU) in a computational system.
-
D.
typicalCPU
Indicates that an entity uses or is associated with a standard or commonly used CPU for its type or category.
-
E.
primarySystem
Indicates that one system is designated as the main or most important system in relation to another system 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a023f290e3081909a465d6cfb79518a |
completed | May 11, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_6a0238d1436c8190ab0251030b01902e |
completed | May 11, 2026, 8:15 p.m. |
Created at: April 29, 2026, 8:15 p.m.