Triple
T8552030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyper Neo Geo 64 |
E202465
|
entity |
| Predicate | graphicsDimension |
P83576
|
FINISHED |
| Object | 3D |
—
|
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: 3D | Statement: [Hyper Neo Geo 64, graphicsDimension, 3D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: graphicsDimension Context triple: [Hyper Neo Geo 64, graphicsDimension, 3D]
-
A.
mainDimension
Indicates the primary or most significant dimension by which something is measured, organized, or characterized within a given context.
-
B.
dimensionOfCurrent
Indicates the dimensional property (such as magnitude or units) associated with the current in a given context.
-
C.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
D.
externalDimension
Indicates that an entity has a measurable size or extent along one or more outer spatial dimensions (such as length, width, or height).
-
E.
includesDimension
Indicates that one entity encompasses or contains a particular dimension or measurable aspect as part of its definition or structure.
- 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_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. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:19 p.m.