Triple
T8472457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Original Amiga chipset |
E200310
|
entity |
| Predicate | standardResolution |
P33105
|
FINISHED |
| Object | 320×256 (PAL) |
—
|
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: 320×256 (PAL) | Statement: [Original Amiga chipset, standardResolution, 320×256 (PAL)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardResolution Context triple: [Original Amiga chipset, standardResolution, 320×256 (PAL)]
-
A.
resolutionStandard
Indicates that something conforms to, or is evaluated against, a specified level or standard of resolution (e.g., detail, clarity, or granularity).
-
B.
standardDefinition
Indicates that something serves as the officially accepted or commonly recognized definition of a term or concept.
-
C.
mainResolution
Indicates that one resolution is the primary or most important resolution associated with a given context or entity.
-
D.
typicalResolution
chosen
Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
-
E.
targetResolution
Indicates the specific resolution or level of detail that an action, process, or system is intended to achieve or operate at.
- 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.