Triple
T29248198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samurai Spirits |
E741491
|
entity |
| Predicate | combatSystemFeature |
P169307
|
FINISHED |
| Object | rage gauge mechanic |
—
|
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: rage gauge mechanic | Statement: [Samurai Spirits, combatSystemFeature, rage gauge mechanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatSystemFeature Context triple: [Samurai Spirits, combatSystemFeature, rage gauge mechanic]
-
A.
weaponFeature
Indicates that one entity is a characteristic, attribute, or functional aspect of a weapon.
-
B.
usesCombatSystem
Indicates that one entity employs or operates a particular combat system in its functioning or behavior.
-
C.
tacticalFeatureUsed
Indicates that a specific tactical feature, maneuver, or capability is employed or brought into play within a tactical situation or operation.
-
D.
methodOfCombat
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
E.
battleSystem
Indicates a relationship where entities are engaged in or governed by a structured combat or conflict-resolution mechanism.
- F. None of above. chosen
Provenance (4 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f67de7792c81909b5e4e812d143624 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 28, 2026, 12:33 p.m.