Triple
T15247702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Divine Support |
E364428
|
entity |
| Predicate | hasKeyWord |
P114902
|
FINISHED |
| Object | nasr (divine help) |
—
|
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: nasr (divine help) | Statement: [The Divine Support, hasKeyWord, nasr (divine help)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyWord Context triple: [The Divine Support, hasKeyWord, nasr (divine help)]
-
A.
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.
-
B.
hasNotableWord
Indicates that an entity is associated with a word or term that is considered notable, distinctive, or significant in some context.
-
C.
hasTerm
Indicates that an entity includes, is associated with, or is defined by a specific term or condition.
-
D.
hasKeyBusiness
Indicates that one entity possesses or is associated with a primary or strategically important business of another entity.
-
E.
hasKeyTermArabic
chosen
Indicates that an entity is associated with a specific key term expressed in the Arabic language.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f4f9d48190b96a7e0c6993cd69 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.