Triple
T34376524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the God who sees me |
E882299
|
entity |
| Predicate | relatedVerse |
P114904
|
FINISHED |
| Object | Genesis 16:13 |
—
|
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: Genesis 16:13 | Statement: [the God who sees me, relatedVerse, Genesis 16:13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedVerse Context triple: [the God who sees me, relatedVerse, Genesis 16:13]
-
A.
associatedWithVerse
chosen
Indicates a relationship where something is linked or connected to a specific verse, typically in a text or scripture.
-
B.
featuresAdditionalVersesBy
Indicates that a work includes extra or bonus verses contributed by another creator beyond the primary one.
-
C.
relatedPsalm
Indicates that one entity is a psalm that is thematically, liturgically, or contextually associated with another entity.
-
D.
verses
Indicates a relationship where one entity competes or is pitted against another, as in an opposition, matchup, or comparison.
-
E.
neighboringVersePrevious
Indicates that one verse immediately precedes another verse in sequence, making it the previous neighboring verse.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:59 a.m.