Triple
T34994607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quran 83:1 |
E1009488
|
entity |
| Predicate | containsKeyWord |
P6841
|
FINISHED |
| Object | وَيْلٌ (woe) |
—
|
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: وَيْلٌ (woe) | Statement: [Quran 83:1, containsKeyWord, وَيْلٌ (woe)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsKeyWord Context triple: [Quran 83:1, containsKeyWord, وَيْلٌ (woe)]
-
A.
containsText
chosen
Indicates that one entity includes the specified text string within its content.
-
B.
hasSetKeyword
Indicates that a set (such as a collection or group) is associated with a specific keyword used to label, categorize, or identify it.
-
C.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
D.
containsExplicitWordInTitle
Indicates that the title of an item includes at least one word that is considered explicit or profane.
-
E.
containsMorpheme
Indicates that one linguistic unit (such as a word or stem) includes a particular morpheme as one of its meaningful subparts.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a009d623f6c8190b702e2892c52fbb2 |
completed | May 10, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_6a009a3050d48190b64567f28e6ea463 |
completed | May 10, 2026, 2:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.