Triple
T38312633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aaron Riley |
E1033733
|
entity |
| Predicate | fightingStyleIncludes |
P131423
|
FINISHED |
| Object | boxing |
—
|
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: boxing | Statement: [Aaron Riley, fightingStyleIncludes, boxing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightingStyleIncludes Context triple: [Aaron Riley, fightingStyleIncludes, boxing]
-
A.
boxingStyleCharacteristic
Indicates that a particular boxing style possesses or is defined by a specific characteristic or attribute.
-
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.
fightingPreference
chosen
Indicates a relationship where one entity has a favored way, style, or choice of engaging in fights or combat relative to others.
-
D.
fencingStyle
Indicates the specific style or discipline of fencing practiced or used by an entity in a fencing-related context.
-
E.
打撃スタイル
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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.