Triple
T11234549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 NCAA Men’s Final Four |
E265908
|
entity |
| Predicate | championshipGameWentToOvertime |
P5853
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2019 NCAA Men’s Final Four, championshipGameWentToOvertime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championshipGameWentToOvertime Context triple: [2019 NCAA Men’s Final Four, championshipGameWentToOvertime, true]
-
A.
championshipGame
Indicates a game that determines the overall champion or winner of a competition or tournament.
-
B.
overtimePlayed
chosen
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
-
C.
championshipGameScore
Indicates the final score achieved by each participant in a championship game.
-
D.
finalAfterExtraTime
Indicates that the final outcome or result is determined after an additional period of extra time beyond the regular duration.
-
E.
introducedOvertimeShootout
Indicates that an overtime shootout format was implemented or brought into use at a particular point in time.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e903b8ec81909f9c89776d35c650 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.