Triple
T3537634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Mario 64 DS |
E74805
|
entity |
| Predicate | supportsSaveFiles |
P203
|
FINISHED |
| Object | multiple |
—
|
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: multiple | Statement: [Super Mario 64 DS, supportsSaveFiles, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSaveFiles Context triple: [Super Mario 64 DS, supportsSaveFiles, multiple]
-
A.
supportsPersistence
Indicates that one entity enables or provides the capability for another entity’s data or state to be stored and retained over time.
-
B.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
C.
supportsExtentsForFiles
Indicates that a system or component provides support for managing or using extent-based storage structures specifically for files.
-
D.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
E.
supportsExternalDrive
Indicates that one entity is capable of working with, recognizing, or providing functionality for an external storage drive.
- 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_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbcc928248190b851f8280d58cfcf |
completed | March 8, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.