Triple
T8552025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyper Neo Geo 64 |
E202465
|
entity |
| Predicate | hardwareFamily |
P17743
|
FINISHED |
| Object | Neo Geo hardware family |
—
|
LITERAL 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: Neo Geo hardware family | Statement: [Hyper Neo Geo 64, hardwareFamily, Neo Geo hardware family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hardwareFamily Context triple: [Hyper Neo Geo 64, hardwareFamily, Neo Geo hardware family]
-
A.
platformFamily
chosen
Indicates that one platform belongs to, or is categorized under, a broader family or group of related platforms.
-
B.
cpuFamily
Indicates that one CPU belongs to, or is categorized under, a particular CPU family or architecture lineage.
-
C.
chipsetFamily
Indicates that one chipset belongs to, or is categorized under, a particular chipset family or series.
-
D.
operatingSystemFamilyMember
Indicates that one operating system belongs to, or is a variant within, a broader operating system family.
-
E.
kernelFamily
Indicates that one kernel is a member of, or derived from, a particular family or class of related kernels.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe886fb788190a73e7c76c4f86409 |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.