Triple
T36153242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yair Rodríguez |
E1045649
|
entity |
| Predicate | hasNotableLossTo |
P204766
|
FINISHED |
| Object | Max Holloway |
E321064
|
NE 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: Max Holloway | Statement: [Yair Rodríguez, hasNotableLossTo, Max Holloway]
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 (5 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbb6ffc08190b75bb92777841b50 |
completed | June 23, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:08 p.m.