Triple

T11574588
Position Surface form Disambiguated ID Type / Status
Subject Ussher Fort E274470 entity
Predicate formerName P65 FINISHED
Object Fort Crèvecœur E280481 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: Fort Crèvecœur | Statement: [Ussher Fort, formerName, Fort Crèvecœur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fort Crèvecœur
Context triple: [Ussher Fort, formerName, Fort Crèvecœur]
  • A. Fort Crèvecœur chosen
    Fort Crèvecœur was a Dutch colonial fort on the Gold Coast in present-day Ghana, historically used as a trading post and military stronghold.
  • B. Fort Lernoult
    Fort Lernoult was a late 18th-century British military fortification in Detroit that played a key role in controlling the Old Northwest frontier.
  • C. Fort Steuben
    Fort Steuben was an 18th-century U.S. military outpost and surveying base on the Ohio River that later gave rise to the city of Steubenville, Ohio.
  • D. Fort Bokar
    Fort Bokar is a prominent 15th-century stone fortress guarding the seaward entrance to Dubrovnik’s Old City walls in Croatia.
  • E. Fort Slocum
    Fort Slocum is a former U.S. military installation that served as a coastal defense and later training and administrative post, now preserved as part of a historic park 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_69d6aae5ac3c81908d2b0a3a665665b2 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d89048120c81908258f984711f7dd4 completed April 10, 2026, 5:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69e713e49f508190b9bad316d68eab42 completed April 21, 2026, 6:06 a.m.
Created at: April 8, 2026, 9:38 p.m.