Triple
T16193257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prophet Yusuf |
E392994
|
entity |
| Predicate | spokeWords |
P122099
|
FINISHED |
| Object | “No blame will there be upon you today” |
—
|
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: “No blame will there be upon you today” | Statement: [Prophet Yusuf, spokeWords, “No blame will there be upon you today”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokeWords Context triple: [Prophet Yusuf, spokeWords, “No blame will there be upon you today”]
-
A.
spokeVia
Indicates that communication or speech occurred through a particular medium, channel, or intermediary.
-
B.
spokeAt
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
-
C.
spokenOn
Indicates that an utterance or speech act occurred at or during a specific time or date.
-
D.
spokenOfAs
Indicates that one entity is referred to, characterized, or talked about in a particular way by another entity or within a given context.
-
E.
spokenAlong
Indicates that two or more languages are used concurrently or within the same context in a particular place, time, or situation.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e222d74d788190a637fdb9b4f184b9 |
completed | April 17, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.