Triple
T8539180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neo Geo CD |
E202151
|
entity |
| Predicate | supportsSaveData |
P31904
|
FINISHED |
| Object | internal memory |
—
|
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: internal memory | Statement: [Neo Geo CD, supportsSaveData, internal memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSaveData Context triple: [Neo Geo CD, supportsSaveData, internal memory]
-
A.
supportsPersistence
chosen
Indicates that one entity enables or provides the capability for another entity’s data or state to be stored and retained over time.
-
B.
supportsCloudSaves
Indicates that one entity provides functionality for storing and retrieving save data in the cloud for another entity.
-
C.
canBeSavedAs
Indicates that one entity is capable of being stored or preserved in the form or format of another entity.
-
D.
savedWith
Indicates that one entity is preserved, stored, or kept together in association with another entity.
-
E.
saveBy
Indicates that one entity preserves, rescues, or protects another entity from loss, harm, or danger.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a7441c8190980c3516073422fe |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:18 p.m.