Triple
T9270164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | جبل عرفة |
E222803
|
entity |
| Predicate | يُقصد من قبل |
P79876
|
FINISHED |
| Object | الحجاج المسلمون |
—
|
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: الحجاج المسلمون | Statement: [جبل عرفة, يُقصد من قبل, الحجاج المسلمون]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يُقصد من قبل Context triple: [جبل عرفة, يُقصد من قبل, الحجاج المسلمون]
-
A.
preludeTo
Indicates that one event, action, or state occurs earlier and serves as an introduction or lead-in to another.
-
B.
intendedWith
chosen
Indicates that one entity is the planned or desired target, recipient, or context for the use or application of another entity.
-
C.
previouslyBasedOn
Indicates that something was formerly derived from, adapted from, or dependent on another source, but is no longer based on it in its current state.
-
D.
heldBefore
Indicates that one entity possessed or maintained control of something at an earlier time than another entity or event.
-
E.
controlledBefore
Indicates that one entity had control or authority over another entity during a time period that occurred earlier than a specified reference time or event.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd078525308190abfb883123742d3f |
completed | April 1, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.