Triple
T7456881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tawaf al-Wada |
E172146
|
entity |
| Predicate | devotionalActs |
P68203
|
FINISHED |
| Object | Supplication |
—
|
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: Supplication | Statement: [Tawaf al-Wada, devotionalActs, Supplication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalActs Context triple: [Tawaf al-Wada, devotionalActs, Supplication]
-
A.
associatedDevotion
Indicates a relationship where one entity is linked to or characterized by a particular devotion, dedication, or religious/spiritual practice connected to another entity.
-
B.
devotionalPracticesInclude
chosen
Indicates that certain devotional practices form a part or subset of a broader set of devotional activities associated with an entity.
-
C.
devotionalObject
Indicates that one entity is used by or associated with another as an object of religious or spiritual devotion.
-
D.
devotionalDayCommon
Indicates that two or more entities share the same religious or spiritual day of devotion or observance.
-
E.
devotionalTitle
Indicates that one entity serves as the devotional or religiously themed title associated with 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f3b0780881909e645160dd49eb57 |
completed | March 27, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:15 p.m.