Triple
T11234555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 NCAA Men’s Final Four |
E265908
|
entity |
| Predicate | tournamentSeedOfChampion |
P68605
|
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: [2019 NCAA Men’s Final Four, tournamentSeedOfChampion, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentSeedOfChampion Context triple: [2019 NCAA Men’s Final Four, tournamentSeedOfChampion, 1]
-
A.
championSeed
Indicates that an entity is designated as the top or primary seed (expected winner) in a competitive event or tournament.
-
B.
seedOfWinner
chosen
Indicates that one entity is the seed or ranking position assigned to the entity that wins a competition or match.
-
C.
runnerUpSeed
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.
-
D.
playoffSeed
Indicates the ranking or position a team or player holds in a playoff bracket based on their performance or qualification criteria.
-
E.
topSeedByeToSemifinals
Indicates that the top-seeded participant automatically advances directly to the semifinals without playing earlier rounds.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e903b8ec81909f9c89776d35c650 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.