Triple
T13563707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 12 |
E323977
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Madison, Wisconsin |
E11896
|
NE FINISHED |
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: Madison, Wisconsin | Statement: [U.S. Route 12, connects, Madison, Wisconsin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Madison, Wisconsin Context triple: [U.S. Route 12, connects, Madison, Wisconsin]
-
A.
Madison, Wisconsin, United States
chosen
Madison, Wisconsin, United States is the capital city of Wisconsin, known for its major research university, vibrant cultural scene, and numerous lakes.
-
B.
Madison
Madison is the codename for a later-generation Itanium processor variant developed by Intel for high-end server and enterprise computing.
-
C.
Madison
Madison is a suburban city in northern Alabama known for its proximity to Huntsville and its strong schools and residential communities.
-
D.
Madison
Madison is a coastal town in south-central Connecticut known for its beaches, historic New England charm, and popular Hammonasset Beach State Park.
-
E.
Madison
Madison is a small town that serves as one of the local communities within Madison County.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00bbe848190bb33efe2af528295 |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b058bc688190b3549d1cac6f4576 |
completed | May 3, 2026, 8:30 p.m. |
Created at: April 9, 2026, 9:47 p.m.