Triple

T30355134
Position Surface form Disambiguated ID Type / Status
Subject Al-Rawdah ash-Sharifah E772121 entity
Predicate accessRegulatedThrough P75387 FINISHED
Object time slots for visitors 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: time slots for visitors | Statement: [Al-Rawdah ash-Sharifah, accessRegulatedThrough, time slots for visitors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: accessRegulatedThrough
Context triple: [Al-Rawdah ash-Sharifah, accessRegulatedThrough, time slots for visitors]
  • A. accessIs
    Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
  • B. accessDeterminedBy chosen
    Indicates that the ability to access a resource is governed or controlled by a specified condition, rule, or authority.
  • C. accessRestriction
    Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
  • D. accessStatus
    Indicates the current level or state of permission or availability for accessing a resource or entity.
  • E. controlsAccessTo
    Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
  • 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_69f2248c6f5c8190a6177842bf791a3c completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6f8565134819096aac0175f924a9f completed May 3, 2026, 7:25 a.m.
PD Predicate disambiguation batch_69f6f65fd1d08190b88e5e68ba268500 completed May 3, 2026, 7:16 a.m.
Created at: April 29, 2026, 7:56 p.m.