Triple
T26021070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twitch Bits |
E647153
|
entity |
| Predicate | purchasedWith |
P9052
|
FINISHED |
| Object | real money |
—
|
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: real money | Statement: [Twitch Bits, purchasedWith, real money]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purchasedWith Context triple: [Twitch Bits, purchasedWith, real money]
-
A.
purchasedIn
Indicates that a purchasing event occurred within or at a specific location or context (such as a store, city, or country).
-
B.
beganWithPurchaseOf
Indicates that an event, process, or relationship started as a result of, or was initiated by, a purchase.
-
C.
canBePurchasedWith
chosen
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
D.
isPurchasedBy
Indicates that one entity is bought or acquired in a transaction by another entity.
-
E.
purchasedFrom
Indicates that one entity bought or acquired something from another entity as the seller or source.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605e5af4081909e3862d44e313d7f |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:03 a.m.