Triple

T26072204
Position Surface form Disambiguated ID Type / Status
Subject Vrijthof E657579 entity
Predicate isFamousForTourists P95395 FINISHED
Object yes 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: yes | Statement: [Vrijthof, isFamousForTourists, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isFamousForTourists
Context triple: [Vrijthof, isFamousForTourists, yes]
  • A. alsoAttractsTouristsIn
    Indicates that a place, in addition to another, draws or appeals to tourists within a specified location or context.
  • B. inscriptionFamousFor
    Indicates that an inscription is widely recognized or notable specifically because of the referenced feature, event, content, or characteristic.
  • C. isInTownKnownFor
    Indicates that one entity is located in a town that is notable or distinguished for the other entity.
  • D. subjectOfTour chosen
    Indicates that an entity serves as the main focus, destination, or theme of a tour.
  • E. reputedToBeVisitedBy
    Indicates that an entity is commonly believed or reported to be visited by another entity, without necessarily confirming that the visits actually occur.
  • 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_69ee5bbe539081909efc7f9dd7c1b53c completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f606cb4418819089f583e8d030b1c3 completed May 2, 2026, 2:14 p.m.
PD Predicate disambiguation batch_69f5aff889988190ad10bcf1a280f717 completed May 2, 2026, 8:04 a.m.
Created at: April 26, 2026, 7:30 p.m.