Triple
T34180007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Need for Speed: World |
E876785
|
entity |
| Predicate | hasPremiumCurrency |
P10274
|
FINISHED |
| Object | SpeedBoost |
—
|
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: SpeedBoost | Statement: [Need for Speed: World, hasPremiumCurrency, SpeedBoost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPremiumCurrency Context triple: [Need for Speed: World, hasPremiumCurrency, SpeedBoost]
-
A.
hasPremium
Indicates that an entity possesses or is assigned a premium status, feature set, or subscription level relative to a standard offering.
-
B.
isPremium
Indicates that an entity has premium status, typically granting enhanced or paid-tier features or privileges compared to a standard version.
-
C.
hasPremiumFeature
Indicates that an entity possesses or includes a special, higher-tier feature available only in a premium version or plan.
-
D.
isPremiumTierAvailable
Indicates whether access to a premium-level tier or service option is currently available.
-
E.
usesSupplementaryCurrency
chosen
Indicates that an entity employs an additional, non-primary currency alongside its main currency for transactions or value exchange.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a02f847b9848190a9fedbc411ae0918 |
completed | May 12, 2026, 9:52 a.m. |
| PD | Predicate disambiguation | batch_6a02f556860c8190b2995433fa05fdd0 |
completed | May 12, 2026, 9:39 a.m. |
Created at: May 1, 2026, 1:54 a.m.