Triple
T26098394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yalamlam |
E658334
|
entity |
| Predicate | miqatFor |
P76729
|
FINISHED |
| Object | people coming from the direction of Yemen |
—
|
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: people coming from the direction of Yemen | Statement: [Yalamlam, miqatFor, people coming from the direction of Yemen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: miqatFor Context triple: [Yalamlam, miqatFor, people coming from the direction of Yemen]
-
A.
hasSpecificMiqat
chosen
Indicates that a particular pilgrimage or pilgrim is associated with a specific miqat (designated boundary point for entering the state of ihram).
-
B.
qiblihFor
Indicates a directional or locational relationship specifying that something is oriented toward, aligned with, or designated for a particular qiblih (direction of prayer).
-
C.
موقعه_التقريبي
Indicates an approximate or rough location of an entity relative to a place or area.
-
D.
positionOnKaaba
Indicates that one entity occupies a specific location or placement on the surface or structure of the Kaaba.
-
E.
roleInMecca
Indicates that an entity holds or performs a specific role, function, or position in the context of Mecca.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f607381a8c8190ad11235c85be02e1 |
completed | May 2, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:53 p.m.