Triple
T28810797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 NCAA Division I men's basketball tournament |
E727505
|
entity |
| Predicate | runnerUpRegion |
P44527
|
FINISHED |
| Object | West 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: West Region | Statement: [2021 NCAA Division I men's basketball tournament, runnerUpRegion, West Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runnerUpRegion Context triple: [2021 NCAA Division I men's basketball tournament, runnerUpRegion, West Region]
-
A.
regionOfRunnerUp
chosen
Indicates the geographic region associated with the runner-up in a competition or event.
-
B.
runnerUp
Indicates that one entity finished in second place relative to another in a competition or ranking.
-
C.
runnerUpCountry
Indicates the country that finished in second place in a competition or ranking.
-
D.
runnerUpDivision
Indicates that one entity is the second-place finisher (runner-up) within a specified division or category relative to another entity.
-
E.
runnerUpRank
Indicates the position or ranking assigned to an entity that finishes immediately after the winner (or near the top) in a competition or ordered list.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658ef66908190a921624ff271359c |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:30 a.m.