Triple
T31871913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo Geo |
E813625
|
entity |
| Predicate | arcadeSystemVariant |
P172677
|
FINISHED |
| Object | Neo Geo MVS |
—
|
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: Neo Geo MVS | Statement: [Neo Geo, arcadeSystemVariant, Neo Geo MVS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arcadeSystemVariant Context triple: [Neo Geo, arcadeSystemVariant, Neo Geo MVS]
-
A.
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).
-
B.
arcadeSystemGeneration
Indicates the generation or hardware era of an arcade system to which an entity belongs or for which it was designed.
-
C.
notableArcadeGame
Indicates that the subject is an arcade game that is particularly famous, influential, or otherwise noteworthy.
-
D.
arcadeReleaseYear
Indicates the year in which an arcade version of something (typically a game) was first released.
-
E.
arcadeHardwareDeveloper
Indicates that an entity is responsible for designing or developing hardware used in arcade game systems.
- F. None of above. chosen
Provenance (4 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_69f6b09ee1e88190a04d42b8251eaa13 |
completed | May 3, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:54 p.m.