Triple
T30961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division I FCS |
E617
|
entity |
| Predicate | nationalChampionshipGameSite |
P128
|
FINISHED |
| Object | predetermined neutral site (varies by contract) |
—
|
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: predetermined neutral site (varies by contract) | Statement: [NCAA Division I FCS, nationalChampionshipGameSite, predetermined neutral site (varies by contract)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalChampionshipGameSite Context triple: [NCAA Division I FCS, nationalChampionshipGameSite, predetermined neutral site (varies by contract)]
-
A.
notableRivalry
Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
-
B.
homeStadium
Indicates that a particular stadium serves as the primary venue where a sports team plays its home games.
-
C.
ceremonyLocation
chosen
Indicates the place where a ceremony is held or takes place.
-
D.
sharesStadiumWith
Indicates that two teams or organizations use the same stadium as their home or primary venue.
-
E.
formerHomeArena
Indicates that a venue previously served as the primary home arena for a team or organization but no longer holds that status.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490d80a0819083bf604c1229e903 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a2486eb01881909241540dda28e1ff |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.