Triple
T19082738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiferet |
E467069
|
entity |
| Predicate | associatedWithDivineAttribute |
P57193
|
FINISHED |
| Object | Rachamim (mercy) |
—
|
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: Rachamim (mercy) | Statement: [Tiferet, associatedWithDivineAttribute, Rachamim (mercy)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDivineAttribute Context triple: [Tiferet, associatedWithDivineAttribute, Rachamim (mercy)]
-
A.
associatedWithGod
Indicates a relationship in which an entity is linked, related, or connected in some meaningful way to a god or deity.
-
B.
attributeOfDeity
chosen
Indicates that something is a characteristic, quality, or property belonging to a deity.
-
C.
positionOnDivineAttributes
Indicates a stance or view that an entity holds regarding the nature, qualities, or characteristics attributed to the divine.
-
D.
associatedDeityOrForce
Indicates that one entity is linked to, represented by, or under the influence of a particular deity or supernatural force.
-
E.
associatedWithBlessing
Indicates a relationship in which an entity is connected to, linked with, or characterized by a blessing or act of blessing.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2eab58c8190a987c88d633c92ec |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.