Triple
T1473582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hajj |
E27189
|
entity |
| Predicate | alternativeForIncapable |
P18099
|
FINISHED |
| Object | delegated Hajj (Hajj al-Badal) |
—
|
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: delegated Hajj (Hajj al-Badal) | Statement: [Hajj, alternativeForIncapable, delegated Hajj (Hajj al-Badal)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeForIncapable Context triple: [Hajj, alternativeForIncapable, delegated Hajj (Hajj al-Badal)]
-
A.
alternativeForm
chosen
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
B.
cannot
Indicates that one entity lacks the ability, permission, or possibility to perform an action or participate in a specified relationship with another entity.
-
C.
alternativeMother
Indicates that one entity serves as an alternative or substitute mother to another entity.
-
D.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
E.
alternativeLaunchMethod
Indicates that there exists a different or non-standard method by which the launch of something can be 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_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.