Triple
T36930683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 24 |
E913469
|
entity |
| Predicate | containsSpeech |
P56446
|
FINISHED |
| Object | Servant’s prayer to YHWH |
—
|
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: Servant’s prayer to YHWH | Statement: [Genesis 24, containsSpeech, Servant’s prayer to YHWH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpeech Context triple: [Genesis 24, containsSpeech, Servant’s prayer to YHWH]
-
A.
includesSpeech
chosen
Indicates that one entity contains, features, or incorporates spoken language or dialogue as part of its content or behavior.
-
B.
hasSpeech
Indicates that an entity produces, delivers, or is associated with a spoken utterance or verbal expression.
-
C.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
D.
hasSpeechMode
Indicates that an entity is associated with, or operates using, a particular mode or style of speech or vocal communication.
-
E.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0160834e388190908591b300954d29 |
completed | May 11, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_6a01602a83408190a11d754bdc7da0e9 |
completed | May 11, 2026, 4:50 a.m. |
Created at: May 3, 2026, 4:13 p.m.