Triple
T35429698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 248/6 |
E1024019
|
entity |
| Predicate | associatedBiblicalChapter |
P111153
|
FINISHED |
| Object | Matthew 2 |
E1653129
|
NE 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 2 | Statement: [248/6, associatedBiblicalChapter, Matthew 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedBiblicalChapter Context triple: [248/6, associatedBiblicalChapter, Matthew 2]
-
A.
associatedWithBiblicalChapter
chosen
Indicates that something has a specified connection or linkage to a particular chapter in the Bible.
-
B.
associatedBiblicalBook
Indicates that one entity is linked or connected to a specific book of the Bible as its relevant or referenced scriptural source.
-
C.
associatedWithVerse
Indicates a relationship where something is linked or connected to a specific verse, typically in a text or scripture.
-
D.
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.
-
E.
associatedBiblicalFigure
Indicates that one entity is linked or connected to a particular biblical figure, such as by reference, attribution, or traditional association.
- F. None of above.
Provenance (4 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3836bb15a88190bd3000e85f368548 |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.