Triple
T35386194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toad Houses in Super Mario Bros. 3 |
E1022798
|
entity |
| Predicate | rewardUsageContext |
P146363
|
FINISHED |
| Object | world map inventory |
—
|
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: world map inventory | Statement: [Toad Houses in Super Mario Bros. 3, rewardUsageContext, world map inventory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rewardUsageContext Context triple: [Toad Houses in Super Mario Bros. 3, rewardUsageContext, world map inventory]
-
A.
rewardUse
Indicates that one entity grants or provides a reward in response to the use or utilization of another entity.
-
B.
promotionUsage
Indicates that a promotion is being applied or used in relation to a particular transaction, context, or entity.
-
C.
realmUsage
Indicates how a particular realm, domain, or scope is used or applied in relation to another entity or context.
-
D.
rewardScope
chosen
Indicates the extent, range, or conditions under which a reward applies within a given context or system.
-
E.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f794f649648190a79d90e6e67fe2dc |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.