Triple
T26106934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ar-Rahman |
E658560
|
entity |
| Predicate | mercyType |
P159956
|
FINISHED |
| Object | mercy for all beings |
—
|
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: mercy for all beings | Statement: [Ar-Rahman, mercyType, mercy for all beings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mercyType Context triple: [Ar-Rahman, mercyType, mercy for all beings]
-
A.
mercyRule
Indicates that a game is ended early because one side has achieved a lead so large that continuing is deemed unnecessary or unsporting.
-
B.
martyr
Indicates that an entity is killed or suffers greatly, typically for a belief, cause, or principle, often being regarded or treated as a martyr as a result.
-
C.
მეუღლე
Indicates a spousal relationship between two people, where each is the legally or socially recognized husband or wife of the other.
-
D.
sacrificeType
Indicates the specific kind or category of sacrifice involved in a sacrificial action or relationship.
-
E.
subjectOfTribute
Indicates that one entity is the target or honoree of a tribute, such as a payment, offering, or act of respect made by another entity.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f607782ce48190a57ade3cfe455c89 |
completed | May 2, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 7:59 p.m.