Triple
T25201814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mobius Digital |
E631142
|
entity |
| Predicate | hasGameGenreFocus |
P53697
|
FINISHED |
| Object | science fiction 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: science fiction games | Statement: [Mobius Digital, hasGameGenreFocus, science fiction games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameGenreFocus Context triple: [Mobius Digital, hasGameGenreFocus, science fiction games]
-
A.
gameGenreContext
chosen
Indicates the genre or type of game associated with a given game entity or gaming context.
-
B.
hasTargetGenreCategory
Indicates that something is associated with or classified under a specific target genre category.
-
C.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
D.
hasNotableVersionGenre
Indicates that an entity has a specific version or edition that is associated with a notable genre.
-
E.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474b904f48190be6513788f89c6a9 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 12:51 p.m.