Triple
T33422816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EA Mobile |
E855887
|
entity |
| Predicate | usesMonetizationModel |
P94216
|
FINISHED |
| Object | in-app purchases |
—
|
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: in-app purchases | Statement: [EA Mobile, usesMonetizationModel, in-app purchases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMonetizationModel Context triple: [EA Mobile, usesMonetizationModel, in-app purchases]
-
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.
requiresRevenueSharingWith
Indicates that one party must share a portion of its revenue with another party as a condition of their relationship or agreement.
-
D.
usesBillingModel
Indicates that one entity applies or operates under a particular billing model for charging or pricing purposes.
-
E.
usesRevenueModel
chosen
Indicates that one entity applies or operates according to a particular revenue model to generate income.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:36 a.m.