Triple
T1458392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saudia |
E31450
|
entity |
| Predicate | religiousTrafficFocus |
P21643
|
FINISHED |
| Object | Hajj pilgrims |
—
|
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: Hajj pilgrims | Statement: [Saudia, religiousTrafficFocus, Hajj pilgrims]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousTrafficFocus Context triple: [Saudia, religiousTrafficFocus, Hajj pilgrims]
-
A.
religiousTarget
Indicates that an action, policy, or behavior is directed at someone or something specifically because of their religion or religious affiliation.
-
B.
religiousTrend
Indicates a pattern or direction of change over time in religious beliefs, practices, or affiliations among entities.
-
C.
religionSignificant
Indicates that a particular religion plays an important or influential role in relation to the referenced entity or context.
-
D.
religiousActivity
chosen
Indicates participation in, performance of, or association with practices, rituals, or behaviors related to a religion or faith tradition.
-
E.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation to another entity.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59a462881908e84b27846a6bc04 |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.