Triple
T7328125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Especially Merciful |
E168924
|
entity |
| Predicate | appearsInPhrase |
P795
|
FINISHED |
| Object | Bismillah ar-Rahman ar-Rahim |
—
|
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: Bismillah ar-Rahman ar-Rahim | Statement: [The Especially Merciful, appearsInPhrase, Bismillah ar-Rahman ar-Rahim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInPhrase Context triple: [The Especially Merciful, appearsInPhrase, Bismillah ar-Rahman ar-Rahim]
-
A.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
B.
usedPhrase
Indicates that one entity employed or expressed a particular phrase in speech, writing, or another form of communication.
-
C.
appearsIn
chosen
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
D.
arisesIn
Indicates that something originates, emerges, or comes into existence within a specified context, source, or location.
-
E.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0a879b88190bef0fb6cbae411ff |
completed | March 27, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.