Triple

T13203772
Position Surface form Disambiguated ID Type / Status
Subject Sailortown area E314304 entity
Predicate hasTimeProperty P73315 FINISHED
Object historically associated with Belfast’s port 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: historically associated with Belfast’s port | Statement: [Sailortown area, hasTimeProperty, historically associated with Belfast’s port]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTimeProperty
Context triple: [Sailortown area, hasTimeProperty, historically associated with Belfast’s port]
  • A. hasTimeOptions
    Indicates that an entity is associated with one or more selectable time choices or configurations.
  • B. hasTimeStart
    Indicates that an event, process, or state begins at a specific point in time.
  • C. hasTimingCapability
    Indicates that an entity possesses the ability to measure, control, or manage timing-related aspects of an operation or process.
  • D. hasTimeIndication
    Indicates that something includes, specifies, or is associated with a particular time-related indication (such as a timestamp, time period, or temporal marker).
  • E. timeProperty chosen
    Indicates that one entity specifies, constrains, or characterizes a temporal aspect or timing-related attribute of 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_69d806aee7308190b70a237ba2a6e3e1 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98c9961a48190a1157df47f59b7af completed April 10, 2026, 11:49 p.m.
PD Predicate disambiguation batch_69d98bc938f081909f123bdf1263ff7f completed April 10, 2026, 11:46 p.m.
Created at: April 9, 2026, 9:17 p.m.