Triple
T18698105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 NCAA Final Four |
E457172
|
entity |
| Predicate | tournamentSeedOfMichiganState |
P18175
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [2009 NCAA Final Four, tournamentSeedOfMichiganState, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentSeedOfMichiganState Context triple: [2009 NCAA Final Four, tournamentSeedOfMichiganState, 2]
-
A.
cityOfMichiganStateHomeGames
Indicates that the referenced city is the location where Michigan State plays its home games.
-
B.
playoffSeed
chosen
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
-
C.
homeTeamSeed
Indicates the ranking or seed assigned to the home team within a tournament or competition bracket.
-
D.
visitingTeamConferenceSeed
Indicates the ranking or seed assigned to the visiting team within its conference for a given competition or season.
-
E.
regularSeasonTopSeedConference
Indicates that an entity was the highest-ranked (top-seeded) team in its conference during the regular season.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e984988190ae902d41edd8faff |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.