Triple

T15391971
Position Surface form Disambiguated ID Type / Status
Subject Black Ball Ferry Line E368066 entity
Predicate usesVessel P880 FINISHED
Object MV Coho E1155361 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: MV Coho | Statement: [Black Ball Ferry Line, usesVessel, MV Coho]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MV Coho
Context triple: [Black Ball Ferry Line, usesVessel, MV Coho]
  • A. MV Coho chosen
    MV Coho is a passenger and vehicle ferry best known for operating the international route between Port Angeles, Washington, and Victoria, British Columbia.
  • B. MV Wenatchee
    MV Wenatchee is a Jumbo Mark II-class passenger and vehicle ferry operated by Washington State Ferries on routes across Puget Sound.
  • C. MV Samish
    MV Samish is a modern Olympic-class car and passenger ferry operated by Washington State Ferries in Puget Sound.
  • D. MV Arlanza
    MV Arlanza was a British ocean liner built by the renowned shipbuilding company Harland and Wolff for passenger and cargo service in the mid-20th century.
  • E. MV Chimacum
    MV Chimacum is a Washington State Ferries vessel that serves as a modern car and passenger ferry in the Puget Sound region.
  • 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_69d85a1551a08190ba2caea7cd51c639 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e7838b48190862b43c6c8620692 completed April 16, 2026, 1:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff1a6d35148190aa4dc0c2a7bf849d completed May 9, 2026, 11:28 a.m.
Created at: April 10, 2026, 3:19 a.m.