Triple
T23620172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospel of Mark 15:26 |
E583294
|
entity |
| Predicate | immediatePrecededBy |
P80614
|
FINISHED |
| Object | Gospel of Mark 15:25 |
—
|
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: Gospel of Mark 15:25 | Statement: [Gospel of Mark 15:26, immediatePrecededBy, Gospel of Mark 15:25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immediatePrecededBy Context triple: [Gospel of Mark 15:26, immediatePrecededBy, Gospel of Mark 15:25]
-
A.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
B.
predecessorRelationship
chosen
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
-
C.
predecessorRelations
Indicates that one entity comes before another in an ordered sequence or lineage, serving as its predecessor.
-
D.
hasPredecessorRoleIn
Indicates that one role functioned earlier in time or sequence relative to another role within the same context or position.
-
E.
precursorActivity
Indicates that one activity occurs earlier and contributes causally or preparatorily to the initiation of another activity.
- 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_69e248fbcd9081908ba08913f9d30826 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b178d20c819094b547c6c7ae6c01 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:45 p.m.