Triple
T29871883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii Points |
E758612
|
entity |
| Predicate | purchaseEndedOn |
P84767
|
FINISHED |
| Object | 2018-03-26 (end of adding Wii Points to accounts) |
—
|
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: 2018-03-26 (end of adding Wii Points to accounts) | Statement: [Wii Points, purchaseEndedOn, 2018-03-26 (end of adding Wii Points to accounts)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purchaseEndedOn Context triple: [Wii Points, purchaseEndedOn, 2018-03-26 (end of adding Wii Points to accounts)]
-
A.
purchaseFunctionEndDate
chosen
Indicates the date on which a purchase-related function, service, or entitlement comes to an end.
-
B.
concludedAfter
Indicates that one event or process finishes at a time later than the completion of another event or process.
-
C.
soldUntil
Indicates that the availability or sale of an item continues up to, but not beyond, a specified time or date.
-
D.
lastSeenPurchasing
Indicates the most recent time an entity was observed or recorded making a purchase.
-
E.
purchaseTiming
Indicates the point in time or temporal pattern at which a purchase occurs relative to other events or conditions.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676c6e60c8190925e63bd3221cfd9 |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:54 p.m.