Triple
T20184000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scheumann Stadium |
E492805
|
entity |
| Predicate | city |
P40
|
FINISHED |
| Object | Muncie |
—
|
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: Muncie | Statement: [Scheumann Stadium, city, Muncie]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Muncie Context triple: [Scheumann Stadium, city, Muncie]
-
A.
Muncie
chosen
Muncie is a mid-sized city in east-central Indiana known as the home of Ball State University and for its role as a classic American "Middletown" in sociological studies.
-
B.
Atlanta, Indiana
Atlanta, Indiana is a small rural town in central Indiana known for its close-knit community and annual New Earth Festival.
-
C.
Boston, Indiana
Boston, Indiana is a small rural community located in Wayne County in the eastern part of the state near the Ohio border.
-
D.
Evansville
Evansville is a major city in southwestern Indiana located along the Ohio River and serving as a regional economic and cultural hub.
-
E.
Kokomo, Indiana
Kokomo, Indiana is a mid-sized industrial city in central Indiana known historically for its automotive manufacturing and technological innovation.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668f199688190a42094cce220f6f2 |
completed | April 20, 2026, 5:57 p.m. |
Created at: April 11, 2026, 11:36 p.m.