Triple
T8990052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rawdah |
E214764
|
entity |
| Predicate | hasPilgrimageRelation |
P16196
|
FINISHED |
| Object | visited during Hajj |
—
|
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: visited during Hajj | Statement: [Rawdah, hasPilgrimageRelation, visited during Hajj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrimageRelation Context triple: [Rawdah, hasPilgrimageRelation, visited during Hajj]
-
A.
hasPilgrimageType
Indicates that an entity is associated with a specific type or category of pilgrimage.
-
B.
hasPilgrimageActivity
Indicates that an entity engages in, organizes, or is associated with a religious pilgrimage activity.
-
C.
pilgrimageObligationAppliesTo
Indicates that the duty or requirement to perform a pilgrimage applies to a particular entity.
-
D.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
E.
pilgrimageAssociatedWith
chosen
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc68733548819096a5ba0ff41e43da |
completed | April 1, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:04 p.m.