Triple
T8472466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Original Amiga chipset |
E200310
|
entity |
| Predicate | maxColorsHAM |
P30793
|
FINISHED |
| Object | 4096 |
—
|
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: 4096 | Statement: [Original Amiga chipset, maxColorsHAM, 4096]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxColorsHAM Context triple: [Original Amiga chipset, maxColorsHAM, 4096]
-
A.
maxColorsOnScreen
chosen
Indicates the maximum number of distinct colors that can be displayed on the screen at the same time.
-
B.
hasColorExcess
Indicates that an entity exhibits a measured amount of color excess, typically representing the difference between its observed color and its intrinsic or expected color.
-
C.
hasColorRange
Indicates that an entity possesses or is associated with a specific span or set of colors, rather than a single discrete color.
-
D.
simultaneousColors
Indicates that two or more color-related events or states occur at the same time.
-
E.
maximumNumber
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f4fbf481909e4fd7c078b27477 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.