Triple
T14549064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Betsie area |
E341364
|
entity |
| Predicate | hasNearbyTown |
P3883
|
FINISHED |
| Object | Beulah, Michigan |
—
|
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: Beulah, Michigan | Statement: [Point Betsie area, hasNearbyTown, Beulah, Michigan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beulah, Michigan Context triple: [Point Betsie area, hasNearbyTown, Beulah, Michigan]
-
A.
Beulah, Michigan
chosen
Beulah, Michigan is a small village in northwestern Michigan known as a gateway to Crystal Lake and nearby outdoor recreation areas.
-
B.
Buckley, Michigan
Buckley, Michigan is a small village located in northern Michigan that serves as a rural community within Wexford County.
-
C.
Elberta, Michigan
Elberta, Michigan is a small village on Lake Michigan in Benzie County known historically as a Great Lakes port and rail terminus.
-
D.
Belding, Michigan
Belding, Michigan is a small city in central Michigan known historically for its silk manufacturing industry and its location along the Flat River.
-
E.
Blaine, Michigan
Blaine, Michigan is a small unincorporated community located within Dickinson County in Michigan’s Upper Peninsula.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2ed2b4c8190945bd26531c71f1f |
completed | April 14, 2026, 9:34 p.m. |
Created at: April 10, 2026, 1:23 a.m.