Triple
T32474788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genealogy of Jesus |
E829941
|
entity |
| Predicate | linkedToProphecy |
P116863
|
FINISHED |
| Object | 2 Samuel 7 |
—
|
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: 2 Samuel 7 | Statement: [Genealogy of Jesus, linkedToProphecy, 2 Samuel 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToProphecy Context triple: [Genealogy of Jesus, linkedToProphecy, 2 Samuel 7]
-
A.
linkedToProphet
Indicates a relationship in which an entity is associated or connected in some meaningful way to a prophet.
-
B.
relatedProphecy
chosen
Indicates that there exists a prophetic connection or foretelling relationship between the entities involved.
-
C.
interpretedAsProphecyBy
Indicates that something (such as an event, statement, or sign) is understood or treated by someone as a prophecy or predictive message about the future.
-
D.
prophecyHeldBy
Indicates that a particular prophecy is possessed, guarded, or maintained by a specific holder.
-
E.
basedOnProphecyBy
Indicates that something occurs, is created, or is decided as a result of guidance, information, or prediction given by a particular prophecy or prophet.
- 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_69f3491ff3b48190b50a7fa00bb05b1f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 1, 2026, 12:58 a.m.