Triple
T20193225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pokémon Stadium |
E493021
|
entity |
| Predicate | saveSupport |
P103270
|
FINISHED |
| Object | Controller Pak |
—
|
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: Controller Pak | Statement: [Pokémon Stadium, saveSupport, Controller Pak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saveSupport Context triple: [Pokémon Stadium, saveSupport, Controller Pak]
-
A.
saveBy
Indicates that one entity preserves, rescues, or protects another entity from loss, harm, or danger.
-
B.
save
Indicates preserving or storing something from loss, harm, or use, often for future benefit or protection.
-
C.
savedWith
Indicates that one entity is preserved, stored, or kept together in association with another entity.
-
D.
saveSystem
Indicates performing an action that preserves or stores the current state or configuration of a system for future use or recovery.
-
E.
supportsCrossSave
chosen
Indicates that an entity allows users to share and continue their progress or data across multiple platforms or devices.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad7270081908ed8513a8363e9b1 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.