Triple
T21975127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atari 400 |
E542685
|
entity |
| Predicate | graphicsModeCount |
P144631
|
FINISHED |
| Object | multiple text and graphics modes |
—
|
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: multiple text and graphics modes | Statement: [Atari 400, graphicsModeCount, multiple text and graphics modes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphicsModeCount Context triple: [Atari 400, graphicsModeCount, multiple text and graphics modes]
-
A.
graphicsModeColors
Indicates the set or configuration of colors supported or used in a particular graphics mode.
-
B.
hasNumberOfMainModes
chosen
Indicates the relationship that specifies how many primary or main modes (e.g., ways of operation or types) are associated with a given entity.
-
C.
hasNumberOfColors
Indicates the quantity of distinct colors associated with an entity.
-
D.
graphicsCapabilities
Indicates the level or type of graphical processing features or performance that an entity supports or provides.
-
E.
maxColorsOnScreen
Indicates the maximum number of distinct colors that can be displayed on the screen at the same time.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12487a1a88190abb8a51fcd533b6a |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:03 p.m.