Triple

T1654965
Position Surface form Disambiguated ID Type / Status
Subject Millard County E35776 entity
Predicate contains P35 FINISHED
Object Cove Fort E184563 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: Cove Fort | Statement: [Millard County, contains, Cove Fort]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cove Fort
Context triple: [Millard County, contains, Cove Fort]
  • A. Cove Fort chosen
    Cove Fort is a historic 19th-century way station and fort in central Utah that served travelers and mail routes along the Mormon Corridor.
  • B. Fort Narhantes
    Fort Narhantes was a strategically important stronghold that served as the site of a major engagement during the Tuscarora War in early 18th-century colonial North Carolina.
  • C. Fort Sandeman
    Fort Sandeman is the former colonial-era name of the town now known as Zhob in Balochistan, Pakistan.
  • D. Saybrook Fort
    Saybrook Fort was a 17th-century English colonial fortification in present-day Old Saybrook, Connecticut, built to protect settlers and control access to the Connecticut River.
  • E. Fort Fincastle
    Fort Fincastle is an 18th-century limestone fortress in Nassau, Bahamas, built to protect the harbor and now a popular historic landmark and tourist attraction.
  • 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_69a8860568888190a32cd9f70acbba42 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a90a8b597c81908a62b41718d85df6 completed March 5, 2026, 4:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad60ad3bb48190a096ff7813748168 completed March 8, 2026, 11:42 a.m.
Created at: March 4, 2026, 7:29 p.m.