Triple
T25219828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juan Diaz |
E631929
|
entity |
| Predicate | notableBout |
P159052
|
FINISHED |
| Object | Juan Diaz vs. Acelino Freitas |
—
|
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: Juan Diaz vs. Acelino Freitas | Statement: [Juan Diaz, notableBout, Juan Diaz vs. Acelino Freitas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBout Context triple: [Juan Diaz, notableBout, Juan Diaz vs. Acelino Freitas]
-
A.
notableRound
Indicates that an entity is a particularly significant or noteworthy round (e.g., in a competition, tournament, or sequence of events).
-
B.
bearerNotableFight
chosen
Indicates that the bearer has participated in a specific fight or combat event that is considered notable or significant.
-
C.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
-
D.
featuredBout
Indicates that a particular bout or match is highlighted or given special prominence within a card, event, or collection of bouts.
-
E.
notableOpeningEvent
Indicates that an entity had a significant or noteworthy event associated with its opening or inauguration.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 21, 2026, 1:02 p.m.