Triple
T28810796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 NCAA Division I men's basketball tournament |
E727505
|
entity |
| Predicate | championRegion |
P166502
|
FINISHED |
| Object | South Region |
—
|
NE NERFINISHED |
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: South Region | Statement: [2021 NCAA Division I men's basketball tournament, championRegion, South Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championRegion Context triple: [2021 NCAA Division I men's basketball tournament, championRegion, South Region]
-
A.
regionOfLeagueOfLegendsTeam
Indicates the geographic region or competitive area in which a League of Legends team is based or competes.
-
B.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
-
C.
notableTournamentRegion
Indicates that a tournament is notably associated with, recognized in, or significant within a particular geographic region.
-
D.
pairsChampionCountry
Indicates the country that the pairs champion represents or is associated with.
-
E.
clubRegion
Indicates that a club is located in, associated with, or belongs to a particular geographic region.
- F. None of above. chosen
Provenance (4 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6622808b48190bbabcc75288ab031 |
completed | May 2, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f6617a7e7c81908cfac4a2250797ee |
completed | May 2, 2026, 8:41 p.m. |
Created at: April 28, 2026, 6:30 a.m.