Triple
T15383156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Princess Peach |
E367851
|
entity |
| Predicate | hasSaveFeature |
P182
|
FINISHED |
| Object | battery-backed save |
—
|
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: battery-backed save | Statement: [Super Princess Peach, hasSaveFeature, battery-backed save]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSaveFeature Context triple: [Super Princess Peach, hasSaveFeature, battery-backed save]
-
A.
canBeSavedAs
Indicates that one entity is capable of being stored or preserved in the form or format of another entity.
-
B.
hasEditingFeature
Indicates that an entity possesses a capability or function related to modifying or editing content.
-
C.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
D.
supportsCrossSave
Indicates that an entity allows users to share and continue their progress or data across multiple platforms or devices.
-
E.
preservesFeature
Indicates that one entity maintains or keeps intact a particular feature, property, or characteristic of another entity during some process or interaction.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7397188190bde42b897ab4b5b4 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.