Triple

T525624
Position Surface form Disambiguated ID Type / Status
Subject Corsair International E10910 entity
Predicate operatesToDestinationType P6304 FINISHED
Object holiday destinations 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: holiday destinations | Statement: [Corsair International, operatesToDestinationType, holiday destinations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatesToDestinationType
Context triple: [Corsair International, operatesToDestinationType, holiday destinations]
  • A. isDestinationFor
    Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
  • B. operatesOver
    Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
  • C. operatesServiceTo chosen
    Indicates that one entity runs or provides a transportation or service route to another entity or location.
  • D. operatesBy
    Indicates that an entity performs its function, action, or process through the use or application of another entity (e.g., a method, mechanism, or principle).
  • E. hasOperationType
    Indicates the specific kind or category of operation associated with an entity or process.
  • 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_69a2e84b16c4819088d284c47c3a7968 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f1b7f448819087e5e7f3b37d7142 completed Feb. 28, 2026, 1:46 p.m.
PD Predicate disambiguation batch_69a2f0198ecc8190883849e5a8245963 completed Feb. 28, 2026, 1:39 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.