Triple
T17036511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashen |
E413332
|
entity |
| Predicate | combatMechanic |
P39812
|
FINISHED |
| Object | dodge and parry |
—
|
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: dodge and parry | Statement: [Ashen, combatMechanic, dodge and parry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatMechanic Context triple: [Ashen, combatMechanic, dodge and parry]
-
A.
gameplayMechanic
chosen
Indicates a relationship where one entity functions as a rule, system, or interactive feature that defines how another entity can be played or operated within a game.
-
B.
killMechanism
Indicates the method or process by which one entity causes the death or destruction of another.
-
C.
notableLevelMechanic
Indicates that an entity is recognized for its significant involvement in designing, implementing, or innovating game level mechanics.
-
D.
mecha
Indicates a relationship where an entity is a mechanical robot or piloted machine, typically used as a vehicle, weapon, or tool in a technological or sci‑fi context.
-
E.
hasTriggerMechanism
Indicates that an entity possesses or is equipped with a specific mechanism used to initiate or activate an action or process.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f26f50819085dfd0fbecd6394d |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.