Triple

T29763745
Position Surface form Disambiguated ID Type / Status
Subject Chiemsee shipping network E753848 entity
Predicate accessesAttraction P5121 FINISHED
Object Herreninsel royal sites 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: Herreninsel royal sites | Statement: [Chiemsee shipping network, accessesAttraction, Herreninsel royal sites]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: accessesAttraction
Context triple: [Chiemsee shipping network, accessesAttraction, Herreninsel royal sites]
  • A. ridesAttraction
    Indicates that an entity participates in experiencing or using an attraction, such as going on a ride at a venue or amusement location.
  • B. relatedAttraction
    Indicates that one attraction is associated with or connected to another attraction in some relevant way.
  • C. recordAttraction
    Indicates that an instance of an attraction (e.g., interest or appeal) is documented or logged as a record in relation to another entity.
  • D. containsAttraction chosen
    Indicates that one entity includes or encompasses an attraction (such as a point of interest, feature, or draw) within its bounds or scope.
  • E. tourAccess
    Indicates that an entity is permitted to participate in, enter, or make use of a specific tour.
  • 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_69f0ef827ff88190ade56e0b0846b713 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f6bbf6e33c819086e5176d64e7a614 completed May 3, 2026, 3:07 a.m.
PD Predicate disambiguation batch_69f6ba6b1e6c8190adf9d6a257e0b744 completed May 3, 2026, 3 a.m.
Created at: April 28, 2026, 8:35 p.m.