Triple
T26008127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Hearns vs Sugar Ray Leonard I (1981) |
E646815
|
entity |
| Predicate | scheduledRounds |
P159663
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Thomas Hearns vs Sugar Ray Leonard I (1981), scheduledRounds, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheduledRounds Context triple: [Thomas Hearns vs Sugar Ray Leonard I (1981), scheduledRounds, 15]
-
A.
scheduledDuring
Indicates that one event or activity is planned to occur within the time interval defined by another event or period.
-
B.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
C.
seasonRound
Indicates that an event, competition, or activity occurs within a specific round or phase of a season-long sequence.
-
D.
includedRound
Indicates that a particular round is part of, or contained within, a larger set, sequence, or event of rounds.
-
E.
roundsStructure
Indicates that one entity defines or specifies the organization, sequence, or format of rounds within a process, event, or system.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605b366f8819096534cffdd0aa509 |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 9:01 a.m.