Triple
T31871914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo Geo |
E813625
|
entity |
| Predicate | homeConsoleVariant |
P173784
|
FINISHED |
| Object | Neo Geo AES |
—
|
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 AES | Statement: [Neo Geo, homeConsoleVariant, Neo Geo AES]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeConsoleVariant Context triple: [Neo Geo, homeConsoleVariant, Neo Geo AES]
-
A.
hasConsoles
Indicates that one entity possesses, includes, or is equipped with one or more consoles.
-
B.
arcadeSystemVariant
Indicates that one arcade system is a specific version, configuration, or variant derived from another arcade system.
-
C.
launchPlatformVariant
Indicates a relationship where one entity serves as a specific version or type of platform from which another entity is launched.
-
D.
notableConsoleGame
Indicates that a game is recognized as a significant or prominent title released for a particular video game console.
-
E.
appearsInPlatform
Indicates that an entity is present, available, or featured within a particular platform or system.
- 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_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: April 30, 2026, 11:54 p.m.