Triple
T36471285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew 16:19 |
E898544
|
entity |
| Predicate | immediatelyPrecededBy |
P80614
|
FINISHED |
| Object | Matthew 16:18 |
—
|
NE NERFINISHED |
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 16:18 | Statement: [Matthew 16:19, immediatelyPrecededBy, Matthew 16:18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immediatelyPrecededBy Context triple: [Matthew 16:19, immediatelyPrecededBy, Matthew 16:18]
-
A.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
B.
intendedPredecessorOf
Indicates that one entity is meant or planned to come before another in a sequence, order, or process.
-
C.
predecessorRelationship
chosen
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
-
D.
madeByPredecessorOf
Indicates that something was created or produced by an entity that is a predecessor (e.g., earlier version, ancestor, or prior holder of a role) of another specified entity.
-
E.
hasPredecessorRoleIn
Indicates that one role functioned earlier in time or sequence relative to another role within the same context or position.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.