Triple
T1386585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Gospel |
E29858
|
entity |
| Predicate | mayBeReplacedBy |
P28179
|
FINISHED |
| Object | proper Gospel of certain feasts (in older rubrics) |
—
|
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: proper Gospel of certain feasts (in older rubrics) | Statement: [Last Gospel, mayBeReplacedBy, proper Gospel of certain feasts (in older rubrics)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeReplacedBy Context triple: [Last Gospel, mayBeReplacedBy, proper Gospel of certain feasts (in older rubrics)]
-
A.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
B.
seeksToReplace
Indicates an intention or effort by one entity to take over the role, function, or position currently held by another entity.
-
C.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
D.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
E.
replacementName
Indicates that one entity serves as a substitute or successor name for another entity, effectively replacing the original designation.
- F. None of above. chosen
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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c33b6e108190b6b2bca4ddd97b6c |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4beffcf808190ab4cd0271257ce63 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c2f16ae081908c92792253f3eb4b |
completed | March 1, 2026, 10:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.