Triple
T28239344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitchell, South Dakota |
E711975
|
entity |
| Predicate | Corn PalaceLocatedIn |
P164146
|
FINISHED |
| Object | Mitchell, South Dakota |
—
|
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: Mitchell, South Dakota | Statement: [Mitchell, South Dakota, Corn PalaceLocatedIn, Mitchell, South Dakota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Corn PalaceLocatedIn Context triple: [Mitchell, South Dakota, Corn PalaceLocatedIn, Mitchell, South Dakota]
-
A.
stateCapitalBuilding
Indicates that a building serves as the primary governmental capitol facility for a specific state.
-
B.
hasCityHall
Indicates that a location or administrative area possesses or is served by a specific city hall building or institution.
-
C.
countryParkLocatedOn
Indicates that a country park is situated on or within the area of a specified geographic feature or land unit.
-
D.
cityHallOf
Indicates that one entity serves as the official city hall building or administrative center for the specified city.
-
E.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643c3aab88190842770d1bc058c07 |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 10:57 p.m.