Triple
T38282556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ziyarat of Imam Husayn |
E1022115
|
entity |
| Predicate | hasPeakOccasion |
P198179
|
FINISHED |
| Object | Arbaeen pilgrimage |
—
|
NE NERFINISHED |
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: Arbaeen pilgrimage | Statement: [Ziyarat of Imam Husayn, hasPeakOccasion, Arbaeen pilgrimage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakOccasion Context triple: [Ziyarat of Imam Husayn, hasPeakOccasion, Arbaeen pilgrimage]
-
A.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
B.
hasPeakOccupation
Indicates that an entity reached its highest level of activity, prominence, or engagement during a specified time period or context.
-
C.
hasPeakUse
Indicates that something reaches its highest or most intensive level of use during a particular time or condition.
-
D.
hasPeakOver
Indicates that one entity’s peak (such as a maximum value, height, or intensity) exceeds that of another entity.
-
E.
hasPeakAssociated
Indicates that one entity is linked or related to a specific peak (such as a summit or maximum point) associated with it.
- F. None of above. chosen
Provenance (4 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
| PDg | Predicate description generation | batch_69feced436a48190b761db7df2d6b6bd |
completed | May 9, 2026, 6:06 a.m. |
Created at: May 3, 2026, 4:30 p.m.