Triple
T8562479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Totally Games |
E202721
|
entity |
| Predicate | primaryGameType |
P83654
|
FINISHED |
| Object | space flight simulation game |
—
|
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: space flight simulation game | Statement: [Totally Games, primaryGameType, space flight simulation game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGameType Context triple: [Totally Games, primaryGameType, space flight simulation game]
-
A.
primaryGameMode
Indicates the main or default game mode associated with a particular game or gaming context.
-
B.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
C.
ballGameType
Indicates the specific kind or category of ball game associated with an event or activity.
-
D.
includesGameType
Indicates that one entity contains or supports a particular type or category of game.
-
E.
traditionalGame
Indicates that the relationship involves playing, practicing, or being associated with a game that is rooted in longstanding cultural or historical traditions.
- F. None of above. chosen
Provenance (4 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe94c0c3c8190aca981c07b090dc0 |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:20 p.m.