Triple

T389422
Position Surface form Disambiguated ID Type / Status
Subject Jeddah E8848 entity
Predicate pilgrimageRelation P3158 FINISHED
Object entry point for Hajj pilgrims 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: entry point for Hajj pilgrims | Statement: [Jeddah, pilgrimageRelation, entry point for Hajj pilgrims]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: pilgrimageRelation
Context triple: [Jeddah, pilgrimageRelation, entry point for Hajj pilgrims]
  • A. veneratedAt
    Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
  • B. veneratedBy
    Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
  • C. hasReligiousSite
    Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
  • D. religionHistoricallyAssociated
    Indicates a historical association between an entity and a particular religion, based on past practice, tradition, or cultural linkage rather than current or official status.
  • E. relatedPlace chosen
    Indicates a relationship where one place is connected or associated with another place in a relevant or meaningful way.
  • 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_69a2e7f55c60819097aff65ea2ca2832 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec5bdc848190826701590070497b completed Feb. 28, 2026, 1:23 p.m.
PD Predicate disambiguation batch_69a2e96960608190bdd342da9c5ddb5e completed Feb. 28, 2026, 1:11 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.