Triple
T29871893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii Points |
E758612
|
entity |
| Predicate | physicalCardSaleChannels |
P169696
|
FINISHED |
| Object | retail stores |
—
|
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: retail stores | Statement: [Wii Points, physicalCardSaleChannels, retail stores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicalCardSaleChannels Context triple: [Wii Points, physicalCardSaleChannels, retail stores]
-
A.
cardAcceptance
Indicates that one party accepts or recognizes another party’s card as a valid form of payment or identification.
-
B.
cardSlots
Indicates a relationship where specific positions or slots are allocated or available for holding cards.
-
C.
paySystem
Indicates that one entity provides monetary or other compensation to another entity through a particular method, platform, or mechanism.
-
D.
hasPhysicalCard
Indicates that an entity possesses or is associated with a tangible, real-world card object.
-
E.
physicalCardColor
Indicates the relationship between a physical card and the color that characterizes its appearance.
- F. None of above. chosen
Provenance (4 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f68048391c8190abe6580678f8a9ef |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 5:54 p.m.