Triple
T18856406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 24: The Game |
E461179
|
entity |
| Predicate | includesGameplayElement |
P52035
|
FINISHED |
| Object | shooting |
—
|
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: shooting | Statement: [24: The Game, includesGameplayElement, shooting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesGameplayElement Context triple: [24: The Game, includesGameplayElement, shooting]
-
A.
gameElement
chosen
Indicates that one entity functions as a component, feature, or part within the structure or mechanics of a game.
-
B.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
C.
appearsInGameMode
Indicates that an entity is present, available, or featured within a specified game mode.
-
D.
includesGameType
Indicates that one entity contains or supports a particular type or category of game.
-
E.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
- 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c05d0bb8819094d0447441f85b57 |
completed | April 20, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d2166b88190add38de96cedc65c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.