Triple
T29426534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquette Township, Mackinac County, Michigan |
E746309
|
entity |
| Predicate | borderedByBodyOfWaterRegion |
P122362
|
FINISHED |
| Object | Straits of Mackinac |
—
|
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: Straits of Mackinac | Statement: [Marquette Township, Mackinac County, Michigan, borderedByBodyOfWaterRegion, Straits of Mackinac]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByBodyOfWaterRegion Context triple: [Marquette Township, Mackinac County, Michigan, borderedByBodyOfWaterRegion, Straits of Mackinac]
-
A.
connectsToBodyOfWaterRegion
Indicates that a region has a direct physical connection or boundary with a body of water.
-
B.
borderingWaters
chosen
Indicates that a geographic area directly touches or is adjacent to a particular body of water.
-
C.
bordersCountryViaWaterway
Indicates that two countries share a boundary that is defined or connected by a waterway such as a river, canal, or strait.
-
D.
adjacentToBodyOfWater
Indicates that one entity is directly next to or bordering a body of water, such as a lake, river, or ocean.
-
E.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
- F. None of above.
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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 28, 2026, 3:09 p.m.