Triple

T38455554
Position Surface form Disambiguated ID Type / Status
Subject Diriyah Governorate E912303 entity
Predicate hasPlannedAttractions P5121 FINISHED
Object Museums 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: Museums | Statement: [Diriyah Governorate, hasPlannedAttractions, Museums]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlannedAttractions
Context triple: [Diriyah Governorate, hasPlannedAttractions, Museums]
  • A. hasAttractionBasedOn
    Indicates that one entity feels an attraction toward another entity that is specifically grounded in a particular basis, criterion, or set of characteristics.
  • B. isAttractionFor
    Indicates that one entity serves as an attraction or point of interest specifically intended for another entity (such as a person, group, or audience).
  • C. 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.
  • D. hasFestivalAttraction
    Indicates that a festival includes or features a particular attraction as part of its offerings.
  • E. hasAttractionAccess
    Indicates that an entity has permission or the ability to enter, use, or benefit from a specified attraction.
  • 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_69f76e84e2dc81908badf05b3aafa9ea completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fe779248c081909f0ed1a2a0df23db completed May 8, 2026, 11:53 p.m.
PD Predicate disambiguation batch_69fe76eaf6d48190998bc7168749cc42 completed May 8, 2026, 11:51 p.m.
Created at: May 3, 2026, 4:31 p.m.