Triple
T30053478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken Norton vs. George Foreman |
E763662
|
entity |
| Predicate | stoppageTime |
P145607
|
FINISHED |
| Object | 2:00 (approximate) |
—
|
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:00 (approximate) | Statement: [Ken Norton vs. George Foreman, stoppageTime, 2:00 (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stoppageTime Context triple: [Ken Norton vs. George Foreman, stoppageTime, 2:00 (approximate)]
-
A.
stoppedAt
Indicates that an entity has come to a halt or pause at a specific location or point in time.
-
B.
roundOfStoppage
Indicates the specific round in which a contest, match, or event was stopped or ended prematurely.
-
C.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
D.
shutdownPeriod
Indicates a time interval during which a system, service, or process is intentionally turned off or not operational.
-
E.
timeOfStoppageInRound3
chosen
Indicates the specific time point within round 3 at which a stoppage (such as an interruption or end of action) occurs.
- F. None of above.
Provenance (3 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67a18676081908488b1e38d156284 |
completed | May 2, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:56 p.m.