Triple
T29504322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SimCity Social |
E748467
|
entity |
| Predicate | monetizationItem |
P9052
|
FINISHED |
| Object | virtual currency |
—
|
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: virtual currency | Statement: [SimCity Social, monetizationItem, virtual currency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetizationItem Context triple: [SimCity Social, monetizationItem, virtual currency]
-
A.
hasMonetizationFocus
Indicates that one entity is oriented toward or primarily concerned with generating revenue or financial returns from another entity or activity.
-
B.
supportsMonetizationProgram
Indicates that an entity enables or is compatible with a specific monetization program, allowing revenue-generating activities to occur.
-
C.
canBePurchasedWith
chosen
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
D.
promotionSingleFrom
Indicates a relationship where a single item, entity, or offer is being promoted originating from a specific source or context.
-
E.
hasMonetaryComponent
Indicates that something includes, involves, or is associated with a monetary or financial element.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c35c9608190937a51b5de166390 |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:26 p.m.