Triple
T22744812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario's Miracle |
E562518
|
entity |
| Predicate | timeInGame |
P7561
|
FINISHED |
| Object | final seconds of regulation |
—
|
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: final seconds of regulation | Statement: [Mario's Miracle, timeInGame, final seconds of regulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInGame Context triple: [Mario's Miracle, timeInGame, final seconds of regulation]
-
A.
startTimeRelativeToGame
Indicates the time at which an event or action occurs, expressed relative to the start time of the game rather than as an absolute timestamp.
-
B.
typicalGameTime
Indicates the usual or expected amount of time a game takes to play.
-
C.
playTime
Indicates the duration or specific time period during which an entity engages in playing or recreational activity with another entity or object.
-
D.
gameWinningScoreTimeRemaining
chosen
Indicates the amount of time left in the game when the decisive, game-winning score was made.
-
E.
gameLength
Indicates the duration or total length of a game, typically measured in time or turns.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1797590f08190a784f73fcd27b101 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:23 p.m.