Triple
T36959790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydro Thunder |
E914277
|
entity |
| Predicate | originalArcadeHardware |
P205666
|
FINISHED |
| Object | Sega NAOMI |
E1187754
|
NE 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: Sega NAOMI | Statement: [Hydro Thunder, originalArcadeHardware, Sega NAOMI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalArcadeHardware Context triple: [Hydro Thunder, originalArcadeHardware, Sega NAOMI]
-
A.
arcadeHardwareDeveloper
Indicates that an entity is responsible for designing or developing hardware used in arcade game systems.
-
B.
notableArcadeGame
Indicates that the subject is an arcade game that is particularly famous, influential, or otherwise noteworthy.
-
C.
arcadeSystemVariant
Indicates that one arcade system is a specific version, configuration, or variant derived from another arcade system.
-
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.
arcadeSystemGeneration
Indicates the generation or hardware era of an arcade system to which an entity belongs or for which it was designed.
- F. None of above. chosen
Provenance (5 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c3e4e5481909e3a18fdb0bdacc5 |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.