Triple
T6002496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 NCAA men's basketball championship |
E133629
|
entity |
| Predicate | overtimeScore |
P49539
|
FINISHED |
| Object | Kansas 12–5 Memphis |
—
|
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: Kansas 12–5 Memphis | Statement: [2008 NCAA men's basketball championship, overtimeScore, Kansas 12–5 Memphis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overtimeScore Context triple: [2008 NCAA men's basketball championship, overtimeScore, Kansas 12–5 Memphis]
-
A.
overtimePlayed
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
-
B.
regularTimeScore
Indicates the score or performance measure achieved during the standard or non-extended time period of an event or activity.
-
C.
overtimePeriodCount
Indicates the number of overtime periods that occurred or are allocated in a given event or context.
-
D.
overtimePeriodDuration
Indicates the length of time that an overtime period lasts.
-
E.
pointsScored
chosen
Indicates the number of points an entity has earned or achieved in a particular event, game, or context.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee9cb0c8190a3361c36ac3944af |
completed | March 22, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c049e3316c819087ea635fa7ee8472 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.