Triple
T28941834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jam City’s Los Angeles studio |
E730470
|
entity |
| Predicate | gameTypeDeveloped |
P83654
|
FINISHED |
| Object | free-to-play mobile games |
—
|
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: free-to-play mobile games | Statement: [Jam City’s Los Angeles studio, gameTypeDeveloped, free-to-play mobile games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameTypeDeveloped Context triple: [Jam City’s Los Angeles studio, gameTypeDeveloped, free-to-play mobile games]
-
A.
developedGameBasedOn
Indicates that one game was created or designed using another game as its source of inspiration, foundation, or reference.
-
B.
postGamesDevelopment
Indicates that an entity publishes or shares information about the development progress or updates of games.
-
C.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
D.
designedGame
Indicates that one entity is the creator or designer responsible for the conception and development of a particular game.
-
E.
primaryGameType
chosen
Indicates the main category or type of game with which an entity is primarily associated.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65b83d98481909610a07042db3c22 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:37 a.m.