Triple
T7715339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 15:28 |
E174864
|
entity |
| Predicate | containsSpeechAct |
P56446
|
FINISHED |
| Object | divine announcement |
—
|
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: divine announcement | Statement: [Quran 15:28, containsSpeechAct, divine announcement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpeechAct Context triple: [Quran 15:28, containsSpeechAct, divine announcement]
-
A.
speechAct
Indicates that one entity performs a communicative action (such as stating, asking, commanding, or promising) directed toward another entity or audience.
-
B.
includesSpeech
chosen
Indicates that one entity contains, features, or incorporates spoken language or dialogue as part of its content or behavior.
-
C.
isSpokenAlong
Indicates that something (typically a language or dialect) is used or spoken in the regions or areas that follow a particular path, boundary, or route.
-
D.
hasSpeech
Indicates that an entity produces, delivers, or is associated with a spoken utterance or verbal expression.
-
E.
givesSpeechTo
Indicates that one entity delivers a speech or formal address directed toward another entity or audience.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.