Triple
T29248555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACA NeoGeo |
E741499
|
entity |
| Predicate | emulatesHardware |
P31513
|
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: [ACA NeoGeo, emulatesHardware, Neo Geo MVS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emulatesHardware Context triple: [ACA NeoGeo, emulatesHardware, Neo Geo MVS]
-
A.
emulates
chosen
Indicates that one entity imitates or reproduces the behavior, function, or characteristics of another.
-
B.
runsOnHardware
Indicates that a system, software, or process operates using or is executed on a specified hardware platform.
-
C.
hasHardware
Indicates that one entity possesses, includes, or is equipped with specific hardware components or devices.
-
D.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
E.
isOpenHardwareLike
Indicates that something shares key characteristics with open hardware, such as publicly available design files, modifiability, and permission for reuse or reproduction.
- 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_69f6648b128c81908bff08760a8877d4 |
completed | May 2, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:33 p.m.