Triple
T19072231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parable of the Yeast |
E466819
|
entity |
| Predicate | appearsInChapterAndVerse |
P36548
|
FINISHED |
| Object | Matthew 13:33 |
—
|
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: Matthew 13:33 | Statement: [Parable of the Yeast, appearsInChapterAndVerse, Matthew 13:33]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInChapterAndVerse Context triple: [Parable of the Yeast, appearsInChapterAndVerse, Matthew 13:33]
-
A.
associatedWithBiblicalChapter
Indicates that something has a specified connection or linkage to a particular chapter in the Bible.
-
B.
foundInChapter
chosen
Indicates that something (such as a concept, section, or element) is contained within or occurs in a specific chapter.
-
C.
chapterAndVerse
Indicates a relationship where a specific chapter is associated with a specific verse (or set of verses) within a structured text, such as a book or document.
-
D.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
E.
appearsInBookNumber
Indicates that an entity is featured or mentioned in a specific book identified by its number within a series or collection.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19fa6948190bdf8e8ec022e12f2 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.