Triple
T15598498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crystal Lake (Benzie County, Michigan) |
E374968
|
entity |
| Predicate | shorelineSettlement |
P119386
|
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: [Crystal Lake (Benzie County, Michigan), shorelineSettlement, Beulah, Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shorelineSettlement Context triple: [Crystal Lake (Benzie County, Michigan), shorelineSettlement, Beulah, Michigan]
-
A.
shorelineDevelopment
Indicates the extent to which human-made structures or modifications have been built along a shoreline.
-
B.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
C.
shorelineOwnership
Indicates that one entity holds legal or recognized ownership rights over a stretch of shoreline associated with another entity or location.
-
D.
isCoastalSettlementOf
Indicates that a settlement is located on or near the coast within the territory of a specified geographic or administrative area.
-
E.
shorelineLength
Indicates the total measured extent of a land area’s boundary where it meets a body of water.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e609ab081909feb486a57439960 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:12 a.m.