Triple

T6313890
Position Surface form Disambiguated ID Type / Status
Subject Stranraer E141567 entity
Predicate hasFerryHistory P1737 FINISHED
Object Stena Line services to Northern Ireland LITERAL 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: Stena Line services to Northern Ireland | Statement: [Stranraer, hasFerryHistory, Stena Line services to Northern Ireland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFerryHistory
Context triple: [Stranraer, hasFerryHistory, Stena Line services to Northern Ireland]
  • A. hasFerryComponent
    Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
  • B. hasFerryService chosen
    Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
  • C. hasFerryType
    Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
  • D. hasFerryPort
    Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
  • E. hasFerryman
    Indicates that one entity serves as the ferryman (the operator of a ferry or boat that transports others) for another entity.
  • 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_69c008d00efc8190a36c05b4b4a3bf4b completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c064a075dc8190acf7ec010cb4b00c completed March 22, 2026, 9:52 p.m.
PD Predicate disambiguation batch_69c060e311b48190b1c74a5cf9435623 completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:28 p.m.