Triple
T31871924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo Geo |
E813625
|
entity |
| Predicate | arcadeCartridgeSystem |
P91968
|
FINISHED |
| Object | Multi Video System |
—
|
NE NERFINISHED |
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: Multi Video System | Statement: [Neo Geo, arcadeCartridgeSystem, Multi Video System]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arcadeCartridgeSystem Context triple: [Neo Geo, arcadeCartridgeSystem, Multi Video System]
-
A.
arcadeSystemVariant
Indicates that one arcade system is a specific version, configuration, or variant derived from another arcade system.
-
B.
arcadeSystemGeneration
Indicates the generation or hardware era of an arcade system to which an entity belongs or for which it was designed.
-
C.
intendedCartridgeStandard
chosen
Indicates that an item is designed to be used with, or conform to, a particular cartridge standard.
-
D.
arcadeStandard
Indicates that something conforms to, or is defined as, the standard or typical form used in arcade contexts (such as games, machines, or configurations).
-
E.
notableArcadeGame
Indicates that the subject is an arcade game that is particularly famous, influential, or otherwise noteworthy.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:54 p.m.