Triple
T25054629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danny García |
E627480
|
entity |
| Predicate | hasNotableFight |
P159052
|
FINISHED |
| Object | Danny García vs Amir Khan (2012) |
—
|
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: Danny García vs Amir Khan (2012) | Statement: [Danny García, hasNotableFight, Danny García vs Amir Khan (2012)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFight Context triple: [Danny García, hasNotableFight, Danny García vs Amir Khan (2012)]
-
A.
hasNotableBoxer
Indicates that an entity is associated with or characterized by a boxer who is considered notable or distinguished.
-
B.
bearerNotableFight
chosen
Indicates that the bearer has participated in a specific fight or combat event that is considered notable or significant.
-
C.
hasFight
Indicates that one entity engages in a physical or verbal conflict with another entity.
-
D.
hasNotableContender
Indicates that an entity has a significant rival, challenger, or competitor recognized as noteworthy in relation to it.
-
E.
hasNotableHero
Indicates that an entity is associated with a particularly distinguished or prominent hero.
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 18, 2026, 6:09 a.m.