Triple
T30295548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khutbah |
E770509
|
entity |
| Predicate | oftenDeliveredIn |
P182254
|
FINISHED |
| Object | Arabic |
—
|
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: Arabic | Statement: [Khutbah, oftenDeliveredIn, Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenDeliveredIn Context triple: [Khutbah, oftenDeliveredIn, Arabic]
-
A.
oftenArrivesBy
Indicates that one entity typically reaches or comes to another entity or location using a particular means or method.
-
B.
deliveredAt
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
-
C.
deliveredDuring
Indicates that one entity was delivered within the time span defined by another entity or temporal interval.
-
D.
typicalDelivery
Indicates the usual or standard way in which something is delivered, reflecting the most common delivery method or pattern in that context.
-
E.
isCustomarilyDeliveredAfter
Indicates that one item, event, or action is normally or traditionally delivered only after another specified item, event, or action has occurred or been delivered.
- 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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 29, 2026, 7:47 p.m.