Triple
T12844323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007 NCAA Tournament |
E307131
|
entity |
| Predicate | playInGameDate |
P29412
|
FINISHED |
| Object | 2007-03-13 |
—
|
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: 2007-03-13 | Statement: [2007 NCAA Tournament, playInGameDate, 2007-03-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playInGameDate Context triple: [2007 NCAA Tournament, playInGameDate, 2007-03-13]
-
A.
playedOnDate
chosen
Indicates that an event or activity (such as a game, performance, or match) occurred on a specific calendar date.
-
B.
typicalGameDate
Indicates the usual or standard calendar date on which a particular game is played or scheduled to occur.
-
C.
recordGameDate
Indicates that an entity logs or stores the date on which a particular game took place or is scheduled.
-
D.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
-
E.
game1Date
Indicates the calendar date on which the first game or match in a series takes place.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:36 p.m.