Triple
T36961643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headless Kamikaze |
E914321
|
entity |
| Predicate | gameplayCategory |
P142353
|
FINISHED |
| Object | rushdown enemy |
—
|
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: rushdown enemy | Statement: [Headless Kamikaze, gameplayCategory, rushdown enemy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplayCategory Context triple: [Headless Kamikaze, gameplayCategory, rushdown enemy]
-
A.
playsCategory
Indicates that an entity engages in or performs activities belonging to a specified category.
-
B.
gameplayBasis
Indicates that one entity serves as the core mechanic, structure, or inspiration upon which another entity’s gameplay is designed or derived.
-
C.
hasInGameCategory
chosen
Indicates that an in-game item, action, or entity belongs to a specific predefined category within the game’s classification system.
-
D.
boardGameGeekCategory
Indicates that something is classified under a specific category in the BoardGameGeek taxonomy of board game types or themes.
-
E.
primaryGameType
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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.