Triple
T34243380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Need for Speed: Hot Pursuit (2010 video game) |
E878528
|
entity |
| Predicate | primaryGameplayStyle |
P3775
|
FINISHED |
| Object | arcade handling |
—
|
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: arcade handling | Statement: [Need for Speed: Hot Pursuit (2010 video game), primaryGameplayStyle, arcade handling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGameplayStyle Context triple: [Need for Speed: Hot Pursuit (2010 video game), primaryGameplayStyle, arcade handling]
-
A.
primaryGameType
Indicates the main category or type of game with which an entity is primarily associated.
-
B.
primaryGameMode
Indicates the main or default game mode associated with a particular game or gaming context.
-
C.
styleOfPlay
chosen
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
D.
primaryGame
Indicates that one game is the main or most significant game associated with an entity (such as a person, team, or event) among possibly several games.
-
E.
primaryUseByPlayers
Indicates the main way in which players typically use or interact with the referenced entity.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:56 a.m.