Triple
T20320304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woman taken in adultery |
E492190
|
entity |
| Predicate | appearsInVerses |
P11163
|
FINISHED |
| Object | John 7:53–8:11 |
—
|
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: John 7:53–8:11 | Statement: [Woman taken in adultery, appearsInVerses, John 7:53–8:11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInVerses Context triple: [Woman taken in adultery, appearsInVerses, John 7:53–8:11]
-
A.
hasVersesIn
Indicates that one entity (typically a text, chapter, or section) contains or is composed of verses found within another entity (such as a book, collection, or scripture).
-
B.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
C.
associatedWithVerse
Indicates a relationship where something is linked or connected to a specific verse, typically in a text or scripture.
-
D.
positionInScripture
Indicates the specific location or ordering of a passage, verse, or element within a scriptural text.
-
E.
inScripture
chosen
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778b8b648190b80badaf15be2599 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:20 a.m.