Triple
T21911400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvin Hagler vs. Thomas Hearns |
E541070
|
entity |
| Predicate | timeOfStoppageInRound3 |
P145607
|
FINISHED |
| Object | 2:01 |
—
|
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: 2:01 | Statement: [Marvin Hagler vs. Thomas Hearns, timeOfStoppageInRound3, 2:01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfStoppageInRound3 Context triple: [Marvin Hagler vs. Thomas Hearns, timeOfStoppageInRound3, 2:01]
-
A.
roundOfStoppage
Indicates the specific round in which a contest, match, or event was stopped or ended prematurely.
-
B.
thirdRoundEndDate
Indicates the date on which the third round of an event, process, or sequence concludes.
-
C.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
D.
hasThirdRound
Indicates that an entity includes, participates in, or is associated with a third round within a multi-round process or sequence.
-
E.
usesExtraTimeInLaterRounds
Indicates that an entity allocates or consumes additional time during later stages or rounds of an activity, process, or event.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f121da36e88190b42b82641ec54a19 |
completed | April 28, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c187bc548190b4ca13150f6bae38 |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 7:41 p.m.