Triple
T36153242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yair Rodríguez |
E1045649
|
entity |
| Predicate | hasNotableLossTo |
—
|
GENERATED |
| Object | Max Holloway |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLossTo Context triple: [Yair Rodríguez, hasNotableLossTo, Max Holloway]
-
A.
canBeLostBy
Indicates that something is capable of being lost or forfeited by a particular entity.
-
B.
hasNotableStrengthIn
Indicates that an entity possesses a particularly high level of ability, effectiveness, or advantage in a specific area or domain.
-
C.
isLostBy
Indicates that something ceases to be possessed, controlled, or retained by a particular entity.
-
D.
hasNotableScore
Indicates that an entity is associated with a score or rating considered significant or noteworthy in its context.
-
E.
hasNotableHit
Indicates that an entity is associated with a particularly successful, famous, or widely recognized work, performance, or achievement.
- F. None of above. chosen
Provenance (1 batch)
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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.