Triple
T15656711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Bell |
E376459
|
entity |
| Predicate | canBeStored |
P112765
|
FINISHED |
| Object | item reserve in Super Mario 3D World |
—
|
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: item reserve in Super Mario 3D World | Statement: [Super Bell, canBeStored, item reserve in Super Mario 3D World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeStored Context triple: [Super Bell, canBeStored, item reserve in Super Mario 3D World]
-
A.
canBeStoredFor
Indicates that something is suitable or allowed to be kept in storage for a certain duration or under certain conditions.
-
B.
canBeStoredOn
chosen
Indicates that one entity is capable of being placed, kept, or maintained on another entity as a storage location.
-
C.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
D.
canBeShared
Indicates that something is capable of being distributed or accessed by multiple parties.
-
E.
canBeReconstituted
Indicates that something has the capacity to be restored or returned to a prior or functional state, typically after being separated, dissolved, or broken down.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef1f83c8190bbf65eed162cbd55 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.