Triple
T22862806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 NCAA Division I men's basketball championship game |
E566968
|
entity |
| Predicate | tipoffTimeLocal |
P65010
|
FINISHED |
| Object | approximately 9:21 p.m. EDT |
—
|
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: approximately 9:21 p.m. EDT | Statement: [2009 NCAA Division I men's basketball championship game, tipoffTimeLocal, approximately 9:21 p.m. EDT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoffTimeLocal Context triple: [2009 NCAA Division I men's basketball championship game, tipoffTimeLocal, approximately 9:21 p.m. EDT]
-
A.
localKickoffTime
chosen
Indicates the scheduled start time of an event as expressed in a specific local time zone.
-
B.
typicalKickoffTimeEastern
Indicates the usual starting time of an event, expressed in the Eastern Time zone.
-
C.
impactTimeEasternDaylightTime
Indicates the specific time at which an impact occurs, expressed in Eastern Daylight Time.
-
D.
tiebreakerGameDate
Indicates the date on which a tiebreaker game is played or scheduled to occur.
-
E.
impactTimeLocal
Indicates the specific local time at which an impact event occurs or is expected to occur.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17efdc3b08190be03d856aa86b277 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.