Triple
T12654647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Appearance of Christ to Mary Magdalene |
E302252
|
entity |
| Predicate | hasBiblicalEpisode |
P3890
|
FINISHED |
| Object | John 20:11–18 |
—
|
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 20:11–18 | Statement: [The Appearance of Christ to Mary Magdalene, hasBiblicalEpisode, John 20:11–18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiblicalEpisode Context triple: [The Appearance of Christ to Mary Magdalene, hasBiblicalEpisode, John 20:11–18]
-
A.
hasEpisodeAbout
Indicates that a particular episode (such as of a show, podcast, or series) focuses on, discusses, or is centered around a specified subject or topic.
-
B.
hasEpisode
Indicates that something, typically a series or program, includes a specific episode as one of its constituent parts.
-
C.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
D.
hasBiblicalConnection
chosen
Indicates a relationship in which one entity is connected to another through references, themes, origins, or influences derived from the Bible.
-
E.
hasEP
Indicates that an entity possesses, is associated with, or is characterized by a specific EP (e.g., an endpoint, event point, or designated EP resource) in the given context.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:18 p.m.