Triple
T5548932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khamzat Chimaev |
E145476
|
entity |
| Predicate | hasFightingAttribute |
P35675
|
FINISHED |
| Object | high takedown pressure |
—
|
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: high takedown pressure | Statement: [Khamzat Chimaev, hasFightingAttribute, high takedown pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFightingAttribute Context triple: [Khamzat Chimaev, hasFightingAttribute, high takedown pressure]
-
A.
hasFightingStance
Indicates that an entity adopts or is characterized by a particular combat or fighting posture.
-
B.
hasFighter
Indicates that an entity possesses, controls, or is associated with a fighter (such as a combatant, combat vehicle, or fighting unit).
-
C.
methodOfCombat
chosen
Indicates the specific technique, style, or means by which an entity engages in combat or fighting.
-
D.
diesFighting
Indicates that an entity dies as a direct result of engaging in a fight or combat.
-
E.
fightingOutOf
Indicates that an individual is competing or representing themselves in a fight or match while being officially associated with a particular location, camp, or organization.
- 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fe143ec8190bb67d2530c92a419 |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:35 p.m.