Triple
T26452651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floyd Mayweather Jr. vs. Conor McGregor |
E665394
|
entity |
| Predicate | fighter1RecordEnteringBout |
P85268
|
FINISHED |
| Object | 49–0 |
—
|
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: 49–0 | Statement: [Floyd Mayweather Jr. vs. Conor McGregor, fighter1RecordEnteringBout, 49–0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fighter1RecordEnteringBout Context triple: [Floyd Mayweather Jr. vs. Conor McGregor, fighter1RecordEnteringBout, 49–0]
-
A.
fighter1RecordBeforeFight
chosen
Indicates the win-loss-draw record of the first fighter prior to the specified fight.
-
B.
fighter2RecordBeforeFight
Indicates the win-loss-draw record of the second fighter as it stood immediately before the specified fight.
-
C.
fighter1StatusBeforeFight
Indicates the condition or state of the first fighter immediately prior to the start of the fight.
-
D.
championEnteringBout
Indicates that an entity who holds a championship title is entering or participating in a competitive bout or match.
-
E.
fighter2StatusBeforeFight
Indicates the condition or state of the second fighter immediately prior to the fight.
- 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_69ee883d5040819097dd154643005230 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 12:06 a.m.