Triple
T23684532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamebred |
E585126
|
entity |
| Predicate | bearerFightingStyle |
P73075
|
FINISHED |
| Object | striking-focused |
—
|
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: striking-focused | Statement: [Gamebred, bearerFightingStyle, striking-focused]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerFightingStyle Context triple: [Gamebred, bearerFightingStyle, striking-focused]
-
A.
combatStyleAgainst
Indicates the specific way or method one entity uses to fight or engage in combat when facing another entity.
-
B.
fightingPreference
Indicates a relationship where one entity has a favored way, style, or choice of engaging in fights or combat relative to others.
-
C.
hasFightingStance
Indicates that an entity adopts or is characterized by a particular combat or fighting posture.
-
D.
peakFighting
Indicates that an entity is engaging in combat or conflict at the highest or most intense level of its fighting capability.
-
E.
打撃スタイル
chosen
Indicates a relationship where an entity is characterized by or associated with a particular style or manner of striking or hitting.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4fb26c88190a6776e4dfd10d54c |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.