Triple
T25739052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Hearns vs Roberto Durán (1984) |
E648162
|
entity |
| Predicate | fighter2Reach |
P162598
|
FINISHED |
| Object | 67 in |
—
|
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: 67 in | Statement: [Thomas Hearns vs Roberto Durán (1984), fighter2Reach, 67 in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fighter2Reach Context triple: [Thomas Hearns vs Roberto Durán (1984), fighter2Reach, 67 in]
-
A.
fighter1Reach
Indicates the arm length or striking distance available to the first fighter in a comparison or matchup.
-
B.
fighter2
Indicates that the subject is the second participant (opponent) in a fighting or combat relationship or event.
-
C.
fighter2FullName
Indicates the full name of the second fighter involved in a fighting-related relationship or event.
-
D.
fighter1
Indicates that the subject is the first participant or primary combatant in a fight or competitive physical confrontation.
-
E.
fighter2Trainer
Indicates that a person serves as the trainer or coach of a particular fighter.
- F. None of above. chosen
Provenance (4 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f627ad6d4c81909796d39d78e414f9 |
completed | May 2, 2026, 4:34 p.m. |
Created at: April 22, 2026, 3:39 a.m.