Triple
T29182129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Light Phaser |
E739770
|
entity |
| Predicate | supportsGameGenre |
P30020
|
FINISHED |
| Object | light gun shooter |
—
|
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: light gun shooter | Statement: [Light Phaser, supportsGameGenre, light gun shooter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGameGenre Context triple: [Light Phaser, supportsGameGenre, light gun shooter]
-
A.
supportsGames
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
B.
supportedGenre
chosen
Indicates that an entity (such as a system, service, or tool) is capable of handling, providing, or working with a specified genre.
-
C.
supportsGameStyle
Indicates that one entity is compatible with or able to accommodate a particular game style or mode of play.
-
D.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
-
E.
includesGameType
Indicates that one entity contains or supports a particular type or category 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a0311c202408190be88a85337aacf11 |
completed | May 12, 2026, 11:40 a.m. |
| PD | Predicate disambiguation | batch_6a0310b0c9c88190ab218d47d4f432ed |
completed | May 12, 2026, 11:36 a.m. |
Created at: April 28, 2026, 11:58 a.m.