Triple
T33541478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DivinePleasure |
E859080
|
entity |
| Predicate | promisedIn |
P177420
|
FINISHED |
| Object | various religious scriptures |
—
|
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: various religious scriptures | Statement: [DivinePleasure, promisedIn, various religious scriptures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promisedIn Context triple: [DivinePleasure, promisedIn, various religious scriptures]
-
A.
promisedOffspring
Indicates that one entity has made a commitment or vow to provide, have, or ensure the future birth of another entity (an offspring).
-
B.
promisedRegion
Indicates that one entity has pledged or guaranteed a specific region or territory to another entity.
-
C.
promisedFeature
Indicates that one entity has committed to providing or implementing a specific feature for another entity.
-
D.
promotedIn
Indicates that an entity was advanced to a higher rank, position, or status during a specified time or event.
-
E.
keptPromiseTo
Indicates that one entity fulfilled or honored a promise previously made to 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: May 1, 2026, 1:39 a.m.