Triple
T28308588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Haj |
E713935
|
entity |
| Predicate | appliesAfter |
P67762
|
FINISHED |
| Object | completion of the Hajj season |
—
|
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: completion of the Hajj season | Statement: [Al-Haj, appliesAfter, completion of the Hajj season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesAfter Context triple: [Al-Haj, appliesAfter, completion of the Hajj season]
-
A.
appliesToAfter
chosen
Indicates that one entity becomes relevant or applicable only after another specified event, condition, or time has occurred.
-
B.
appliedBefore
Indicates that one action, process, or condition was applied earlier in time than another.
-
C.
appliesToServiceAfter
Indicates that something becomes relevant or effective only after a specified service has been performed or has occurred.
-
D.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
E.
appliedWhen
Indicates the condition, time, or circumstances under which something (such as a rule, action, or effect) becomes applicable or is carried out.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 27, 2026, 11:39 p.m.