Triple
T33331048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1997 NCAA Division I men's basketball championship |
E853405
|
entity |
| Predicate | tournamentSeedRunnerUp |
P44526
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [1997 NCAA Division I men's basketball championship, tournamentSeedRunnerUp, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentSeedRunnerUp Context triple: [1997 NCAA Division I men's basketball championship, tournamentSeedRunnerUp, 1]
-
A.
runnerUpSeed
chosen
Indicates that one entity is the competitor or team assigned the second-best (runner-up) seed or ranking in a tournament or competition relative to another entity.
-
B.
bubbleTournamentRunnerUp
Indicates that an entity finished in second place (runner-up) in a bubble-format tournament.
-
C.
tournamentRunnerUpTeam
Indicates that a team finished in second place in a tournament, just below the champion.
-
D.
runnerUpDivision
Indicates that one entity is the second-place finisher (runner-up) within a specified division or category relative to another entity.
-
E.
inSeasonTournamentRunnerUp
Indicates that an entity finished in second place (runner-up) in an in-season tournament.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:34 a.m.