Triple
T2736038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julio César Chávez |
E60632
|
entity |
| Predicate | boxingStyle |
P8071
|
FINISHED |
| Object | pressure fighter |
—
|
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: pressure fighter | Statement: [Julio César Chávez, boxingStyle, pressure fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boxingStyle Context triple: [Julio César Chávez, boxingStyle, pressure fighter]
-
A.
boxingStance
Indicates the specific posture or positioning a boxer adopts while preparing to fight or engage in boxing actions.
-
B.
martialArt
Indicates that one entity practices, performs, or is associated with a specific martial art style or discipline in relation to another entity.
-
C.
hasFightingStance
chosen
Indicates that an entity adopts or is characterized by a particular combat or fighting posture.
-
D.
shootingStyle
Indicates the characteristic manner or technique with which an entity performs a shooting action (e.g., in sports or photography).
-
E.
isGrapplingArt
Indicates that the subject is a martial art or combat style primarily focused on grappling techniques such as holds, locks, and throws.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb11c66c81909058f2978aa5fae9 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.