Triple
T30741243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of Ether |
E782693
|
entity |
| Predicate | includesProphecy |
P20088
|
FINISHED |
| Object | prophecies of the coming of Christ |
—
|
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: prophecies of the coming of Christ | Statement: [Book of Ether, includesProphecy, prophecies of the coming of Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesProphecy Context triple: [Book of Ether, includesProphecy, prophecies of the coming of Christ]
-
A.
containsProphecyAbout
chosen
Indicates that one entity includes or conveys a prediction or foretelling specifically concerning another entity.
-
B.
givesProphecy
Indicates that one entity delivers or reveals a prophecy to another entity.
-
C.
conditionForProphecy
Indicates that a specific condition or set of conditions must be met for a particular prophecy to be fulfilled, activated, or considered valid.
-
D.
relatedProphecy
Indicates that there exists a prophetic connection or foretelling relationship between the entities involved.
-
E.
returnProphecy
Indicates that an entity gives back or delivers a previously received prophecy to its original source or rightful recipient.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00a15604fc8190b1c280794960f3a4 |
completed | May 10, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_6a00a0f7e77881909ac85755ab0e6329 |
completed | May 10, 2026, 3:15 p.m. |
Created at: April 29, 2026, 8:38 p.m.