Triple

T20809586
Position Surface form Disambiguated ID Type / Status
Subject Moosonee E512260 entity
Predicate transportHubFor P423 FINISHED
Object Fort Albany NE NERFINISHED

How this triple was built (3 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: Fort Albany | Statement: [Moosonee, transportHubFor, Fort Albany]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fort Albany
Context triple: [Moosonee, transportHubFor, Fort Albany]
  • A. Fort Wellington
    Fort Wellington is a historic 19th-century British military fortification in Prescott, Ontario, built to defend the St. Lawrence River and now preserved as a National Historic Site of Canada.
  • B. Fort Wellington
    Fort Wellington is a historic military fortification located on the Cobourg Peninsula in Australia’s Northern Territory, notable for its early 19th-century British colonial presence and interactions with Indigenous communities.
  • C. Fort Strong
    Fort Strong is a former coastal defense fortification in Boston Harbor that played a role in protecting the city and its shipping channels, particularly during the 19th and early 20th centuries.
  • D. Fort Bedford
    Fort Bedford was an 18th-century British frontier fort in present-day Bedford, Pennsylvania, that played a strategic role during the French and Indian War and Pontiac’s Rebellion.
  • E. Fort Carlton
    Fort Carlton was a Hudson’s Bay Company fur trade post in what is now Saskatchewan, Canada, that became a key site in the negotiation of Treaty 6 between the Canadian government and Indigenous peoples.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Fort Albany
Target entity description: Fort Albany is a remote Cree First Nation community in northern Ontario, Canada, located along the Albany River near James Bay.
  • A. Fort Wellington
    Fort Wellington is a historic 19th-century British military fortification in Prescott, Ontario, built to defend the St. Lawrence River and now preserved as a National Historic Site of Canada.
  • B. Fort Wellington
    Fort Wellington is a historic military fortification located on the Cobourg Peninsula in Australia’s Northern Territory, notable for its early 19th-century British colonial presence and interactions with Indigenous communities.
  • C. Fort Strong
    Fort Strong is a former coastal defense fortification in Boston Harbor that played a role in protecting the city and its shipping channels, particularly during the 19th and early 20th centuries.
  • D. Fort Bedford
    Fort Bedford was an 18th-century British frontier fort in present-day Bedford, Pennsylvania, that played a strategic role during the French and Indian War and Pontiac’s Rebellion.
  • E. Fort Carlton
    Fort Carlton was a Hudson’s Bay Company fur trade post in what is now Saskatchewan, Canada, that became a key site in the negotiation of Treaty 6 between the Canadian government and Indigenous peoples.
  • F. None of above. chosen

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_69e0b4cd25088190b48ca9700cd24efc completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2d199888190b8b190c928f510b7 completed April 21, 2026, 12:20 a.m.
Created at: April 16, 2026, 12:40 p.m.