Triple
T1473579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hajj |
E27189
|
entity |
| Predicate | exemptionCondition |
P4330
|
FINISHED |
| Object | chronic illness |
—
|
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: chronic illness | Statement: [Hajj, exemptionCondition, chronic illness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exemptionCondition Context triple: [Hajj, exemptionCondition, chronic illness]
-
A.
exemptionType
chosen
Indicates the specific category or kind of exemption that applies in a given context.
-
B.
authorizationCondition
Indicates the specific rules or requirements that must be satisfied for an action or access to be legally or formally authorized.
-
C.
exemptedJurisdiction
Indicates that one jurisdiction is officially excluded from the application, scope, or requirements that apply to other jurisdictions.
-
D.
obligationCondition
Indicates that one situation or state serves as the condition under which an obligation for an entity becomes active or must be fulfilled.
-
E.
releaseCondition
Indicates the circumstances or requirements under which something is allowed to be released or made available.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.