Triple
T25969602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 NCAA Division I men's basketball tournament |
E645768
|
entity |
| Predicate | finalWentToOvertime |
P35409
|
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 Division I men's basketball tournament, finalWentToOvertime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalWentToOvertime Context triple: [2019 NCAA Division I men's basketball tournament, finalWentToOvertime, true]
-
A.
finalAfterExtraTime
chosen
Indicates that the final outcome or result is determined after an additional period of extra time beyond the regular duration.
-
B.
game7Overtimes
Indicates that a game extended into a seventh overtime period, reflecting an exceptionally prolonged and closely contested match.
-
C.
longestGameOvertimes
Indicates the number of overtime periods played in the longest game (by duration or overtime count) within a given context.
-
D.
hasOvertimeWinningMargin
Indicates that one competitor’s margin of victory over another was achieved specifically during an overtime period.
-
E.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 22, 2026, 8:50 a.m.