Triple
T6001751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CollegeInsider.com Postseason Tournament |
E133612
|
entity |
| Predicate | finalGameSite |
P12513
|
FINISHED |
| Object | hosted on campus of participating team |
—
|
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: hosted on campus of participating team | Statement: [CollegeInsider.com Postseason Tournament, finalGameSite, hosted on campus of participating team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalGameSite Context triple: [CollegeInsider.com Postseason Tournament, finalGameSite, hosted on campus of participating team]
-
A.
championshipGameSite
Indicates the location or venue where a championship game is held.
-
B.
finalGameLeague
Indicates that a game is the concluding or championship match within a particular league or league season.
-
C.
decisiveGameVenue
Indicates the location where the final, outcome-determining game of a series or competition is held.
-
D.
finalsLocation
chosen
Indicates the place where the final stage or concluding event of something (such as a competition or process) takes place.
-
E.
finalReplayVenue
Indicates the venue where a final match is replayed after an initial final did not produce a decisive result.
- 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_69c04ee7c0e08190a6e78969448b070a |
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.