Triple
T36961646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Headless Kamikaze |
E914321
|
entity |
| Predicate | playerCounterplay |
P100355
|
FINISHED |
| Object | shoot from distance |
—
|
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: shoot from distance | Statement: [Headless Kamikaze, playerCounterplay, shoot from distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerCounterplay Context triple: [Headless Kamikaze, playerCounterplay, shoot from distance]
-
A.
counterplay
chosen
Indicates a responsive action or strategy taken to oppose, mitigate, or neutralize another party’s move or advantage.
-
B.
opponentStrategy
Indicates that one entity employs or represents a strategic plan specifically designed to counter or compete against another entity.
-
C.
playerChoiceCount
Indicates the number of choices or options a player has made or is allowed to make in a given context.
-
D.
treatsPlayers
Indicates how an entity behaves toward or interacts with players.
-
E.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
- 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_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:14 p.m.