Triple
T29247951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNK Arcade Classics Vol. 1 |
E741486
|
entity |
| Predicate | originalPlatformOfGames |
P61964
|
FINISHED |
| Object | Neo Geo |
—
|
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 | Statement: [SNK Arcade Classics Vol. 1, originalPlatformOfGames, Neo Geo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPlatformOfGames Context triple: [SNK Arcade Classics Vol. 1, originalPlatformOfGames, Neo Geo]
-
A.
originPlatform
chosen
Indicates the platform, system, or environment from which an entity, event, or piece of data originally comes.
-
B.
gamePlatformCategory
Indicates the classification or type of platform on which a game is available or intended to be played.
-
C.
parentPlatformCompany
Indicates that one company serves as the overarching or owning platform company for another company within a corporate or business structure.
-
D.
appearsInPlatform
Indicates that an entity is present, available, or featured within a particular platform or system.
-
E.
originalPlatformGeneration
Indicates that one platform is the initial or first-generation version from which another platform or subsequent generations are derived.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: April 28, 2026, 12:33 p.m.