Triple
T30586827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo Geo MVS |
E778536
|
entity |
| Predicate | maxSpriteSize |
P82807
|
FINISHED |
| Object | 16x512 pixels |
—
|
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: 16x512 pixels | Statement: [Neo Geo MVS, maxSpriteSize, 16x512 pixels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxSpriteSize Context triple: [Neo Geo MVS, maxSpriteSize, 16x512 pixels]
-
A.
maxSpritesOnScreen
Indicates the maximum number of sprites that are allowed to be displayed on the screen at the same time.
-
B.
spriteSizeSupport
chosen
Indicates that an entity supports handling or displaying sprites at specific sizes or resolutions.
-
C.
maxSpritesPerScanline
Indicates the maximum number of sprites that can be rendered or processed on a single horizontal scanline during drawing or display.
-
D.
maximumResolution
Indicates the highest level of detail or fineness at which something (such as an image, display, or measurement) can be represented or processed.
-
E.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68977c2148190bc9679fdc90ff482 |
completed | May 2, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:23 p.m.