Triple

T25286490
Position Surface form Disambiguated ID Type / Status
Subject Remedy Entertainment E633956 entity
Predicate foundedBy P104 FINISHED
Object Markus Mäki
Markus Mäki is a Finnish game developer best known as a founding figure and longtime leader at Remedy Entertainment, the studio behind titles like Max Payne, Alan Wake, and Control.
E1682785 NE 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: Markus Mäki | Statement: [Remedy Entertainment, foundedBy, Markus Mäki]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Markus Mäki
Triple: [Remedy Entertainment, foundedBy, Markus Mäki]
Generated description
Markus Mäki is a Finnish game developer best known as a founding figure and longtime leader at Remedy Entertainment, the studio behind titles like Max Payne, Alan Wake, and Control.

Provenance (5 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_69e75a9402fc81909362ca85277c06d9 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f48e0921ac8190a4a8fec7be7ad8f6 completed May 1, 2026, 11:27 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10ad4614fc819094428697c033c031 completed May 22, 2026, 7:23 p.m.
NEDg Description generation batch_6a10ae2f577481909be995d38010dcf7 completed May 22, 2026, 7:27 p.m.
NED2 Entity disambiguation (via description) batch_6a10aef10de8819099e12e65f4f9e768 completed May 22, 2026, 7:30 p.m.
Created at: April 21, 2026, 1:19 p.m.