Triple
T2768714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquette, Michigan |
E61399
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Marquette Harbor |
E33565
|
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: Marquette Harbor | Statement: [Marquette, Michigan, hasPort, Marquette Harbor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marquette Harbor Context triple: [Marquette, Michigan, hasPort, Marquette Harbor]
-
A.
Milwaukee Harbor
Milwaukee Harbor is a commercial and recreational port area on Lake Michigan serving the city of Milwaukee, Wisconsin.
-
B.
Marquette Bay
Marquette Bay is a small bay on the shore of Lake Superior adjacent to the city of Marquette in Michigan’s Upper Peninsula.
-
C.
Detroit Harbor
Detroit Harbor is a sheltered natural harbor and ferry port on Washington Island in Door County, Wisconsin, serving as a key access point between the island and mainland.
-
D.
Port of Marquette
chosen
The Port of Marquette is a commercial harbor on Lake Superior that serves as a key shipping point for bulk commodities in Michigan’s Upper Peninsula.
-
E.
Portage Bay
Portage Bay is a small, sheltered arm of Seattle’s Lake Union that serves as a key waterway connecting Lake Washington to the Lake Union–Puget Sound system.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdd6785d88190b99f99889463a962 |
completed | March 7, 2026, 8:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afce89a144819096f9230c8d95ce3f |
completed | March 10, 2026, 7:55 a.m. |
Created at: March 6, 2026, 9:57 p.m.