Triple
T11798511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Transportation Corporation |
E280563
|
entity |
| Predicate | regionServed |
P82
|
FINISHED |
| Object | Detroit central business district |
—
|
NE GENERATED |
How this triple was built (1 step)
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Detroit central business district Context triple: [Detroit Transportation Corporation, regionServed, Detroit central business district]
-
A.
Downtown Detroit
chosen
Downtown Detroit is the central business district and cultural core of Detroit, Michigan, known for its skyscrapers, sports arenas, theaters, and revitalized riverfront.
-
B.
Midtown Detroit
Midtown Detroit is a central cultural and educational district in Detroit, Michigan, known for its museums, universities, and historic architecture.
-
C.
Detroit Downtown Development Authority
The Detroit Downtown Development Authority is a public economic development agency that oversees and promotes redevelopment and investment in Detroit’s central business district.
-
D.
New Center area of Detroit
The New Center area of Detroit is a historic commercial and cultural district just north of downtown, known for its landmark architecture, major corporate offices, and significant role in the city’s automotive and musical heritage.
-
E.
Detroit East Side
Detroit East Side is a predominantly residential area of Detroit, Michigan, historically known for its working-class neighborhoods and significant role in the city’s racial and industrial history.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (1 batch)
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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.