Triple
T18727913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M-24 (Lapeer Road) |
E457954
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Lapeer area |
—
|
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: Lapeer area | Statement: [M-24 (Lapeer Road), connects, Lapeer area]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lapeer area Context triple: [M-24 (Lapeer Road), connects, Lapeer area]
-
A.
Lapeer
Lapeer is a small city in Michigan known as an administrative and commercial center for the surrounding rural region.
-
B.
Grand Ledge, Michigan
Grand Ledge, Michigan is a small city in Eaton County known for its scenic sandstone ledges and parks along the Grand River.
-
C.
City of Lapeer
chosen
The City of Lapeer is a small incorporated community that serves as the county seat and primary urban center of Lapeer County in Michigan.
-
D.
Town of Lapeer
The Town of Lapeer is a small rural municipality located in Cortland County in central New York State.
-
E.
Ecorse, Michigan
Ecorse, Michigan is a small industrial city in Wayne County along the Detroit River, historically known for its steel manufacturing and role in the Downriver Detroit region.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56d759a288190855ade3756e03e04 |
completed | April 20, 2026, 12:04 a.m. |
Created at: April 10, 2026, 11:50 a.m.