Triple
T19286415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copper Harbor, Michigan |
E482323
|
entity |
| Predicate | transportationRouteTerminus |
P116675
|
FINISHED |
| Object | U.S. Route 41 |
—
|
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: U.S. Route 41 | Statement: [Copper Harbor, Michigan, transportationRouteTerminus, U.S. Route 41]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationRouteTerminus Context triple: [Copper Harbor, Michigan, transportationRouteTerminus, U.S. Route 41]
-
A.
transportTerminusFor
chosen
Indicates that a location serves as the endpoint or final stop for a particular transport route or service.
-
B.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
C.
railLineTerminus
Indicates that a rail line ends or terminates at the specified location or station.
-
D.
transportationJunctionFor
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
-
E.
railTerminus
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc024a7081909a25d7cc4e048f79 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.