Triple
T33536808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guinness World Record for most ported video game |
E858956
|
entity |
| Predicate | holderGameGenre |
P83654
|
FINISHED |
| Object | tile-matching puzzle 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: tile-matching puzzle game | Statement: [Guinness World Record for most ported video game, holderGameGenre, tile-matching puzzle game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderGameGenre Context triple: [Guinness World Record for most ported video game, holderGameGenre, tile-matching puzzle game]
-
A.
gameGenreContext
Indicates the genre or type of game associated with a given game entity or gaming context.
-
B.
gameGenreDeveloped
Indicates that a particular game genre has been created, defined, or developed by a specific entity (such as a person, team, or organization).
-
C.
websiteGenre
Indicates the thematic category or type of content that a website is primarily associated with.
-
D.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:39 a.m.