Triple
T25814593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OEMA |
E650213
|
entity |
| Predicate | servesNearbyReligiousSite |
P61457
|
FINISHED |
| Object | Al-Masjid an-Nabawi |
—
|
NE NERFINISHED |
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: Al-Masjid an-Nabawi | Statement: [OEMA, servesNearbyReligiousSite, Al-Masjid an-Nabawi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesNearbyReligiousSite Context triple: [OEMA, servesNearbyReligiousSite, Al-Masjid an-Nabawi]
-
A.
nearReligiousSite
Indicates that one entity is located close to or in the immediate vicinity of a religious site.
-
B.
religiousTextAssociationNearby
Indicates a spatial relationship where a religious text or related object is located close to or in the immediate vicinity of another entity.
-
C.
locatesChurchWithin
Indicates that one entity places or establishes a church within the boundaries or interior of another entity.
-
D.
hasNearbyPilgrimageSite
chosen
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
E.
placeOfWorshipLocation
Indicates the location where a particular place of worship is situated or found.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 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 22, 2026, 7:13 a.m.