Triple
T38483050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 NCAA Division I Men's Basketball Championship Game |
E917835
|
entity |
| Predicate | regionOfLouisville |
P202603
|
FINISHED |
| Object | Midwest 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: Midwest Region | Statement: [2013 NCAA Division I Men's Basketball Championship Game, regionOfLouisville, Midwest Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfLouisville Context triple: [2013 NCAA Division I Men's Basketball Championship Game, regionOfLouisville, Midwest Region]
-
A.
LouisvilleScore
Indicates that a scoring event or point total is attributed to Louisville in a game or competition.
-
B.
regionOfIndiana
Indicates that something is a geographic or administrative area located within the state of Indiana.
-
C.
seedOfLouisville
Indicates the tournament seeding or ranking assigned to Louisville in a given competition or bracket.
-
D.
MemphisRegion
Indicates that something is located in, associated with, or pertains to the Memphis geographic region.
-
E.
locationRelativeToRichmond
Indicates the spatial or geographic position of one place in relation to the reference location Richmond.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a009f53a4948190aef4ede1713e1748 |
completed | May 10, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_6a009edc53d4819080b22c1074a990f3 |
completed | May 10, 2026, 3:06 p.m. |
| PDg | Predicate description generation | batch_6a009f52ef9c8190be0e8ea2e2cd484f |
completed | May 10, 2026, 3:08 p.m. |
Created at: May 3, 2026, 4:31 p.m.