Triple
T30819182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safā and Marwah area |
E784868
|
entity |
| Predicate | hasPilgrimCapacity |
P34540
|
FINISHED |
| Object | very high |
—
|
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: very high | Statement: [Safā and Marwah area, hasPilgrimCapacity, very high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrimCapacity Context triple: [Safā and Marwah area, hasPilgrimCapacity, very high]
-
A.
pilgrimCapacity
chosen
Indicates the maximum number of pilgrims that an entity (such as a facility, vehicle, or location) is designed or allowed to accommodate.
-
B.
hasPilgrims
Indicates that an entity is associated with or contains pilgrims, typically as visitors, members, or participants in a pilgrimage.
-
C.
isPilgrimTo
Indicates that one entity travels to or visits a place as a religious or spiritual pilgrimage in relation to another entity.
-
D.
hasPilgrimType
Indicates that an entity is associated with, classified as, or characterized by a particular type or category of pilgrim.
-
E.
hasStandingCapacity
Indicates that an entity is capable of maintaining or supporting a specified condition, function, or load on an ongoing basis.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 8:44 p.m.