Triple
T30261041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metal Slug Attack |
E769491
|
entity |
| Predicate | hasInGamePurchases |
P37743
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Metal Slug Attack, hasInGamePurchases, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInGamePurchases Context triple: [Metal Slug Attack, hasInGamePurchases, true]
-
A.
hasInAppPurchases
chosen
Indicates that an application offers additional content, features, or services that users can buy from within the app itself.
-
B.
isPurchasedBy
Indicates that one entity is bought or acquired in a transaction by another entity.
-
C.
hasInGameActivities
Indicates that an entity includes or offers specific activities or actions that can be performed within a game context.
-
D.
canBePurchased
Indicates that one entity is available to be bought or acquired in exchange for payment by another entity.
-
E.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: April 29, 2026, 7:42 p.m.