Triple
T11056349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anamnesis |
E261385
|
entity |
| Predicate | isLocatedAfter |
P4527
|
FINISHED |
| Object | institution narrative in the Eucharistic Prayer |
—
|
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: institution narrative in the Eucharistic Prayer | Statement: [Anamnesis, isLocatedAfter, institution narrative in the Eucharistic Prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedAfter Context triple: [Anamnesis, isLocatedAfter, institution narrative in the Eucharistic Prayer]
-
A.
locatedAfter
chosen
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
B.
appliesToAfter
Indicates that one entity becomes relevant or applicable only after another specified event, condition, or time has occurred.
-
C.
laterInstanceOf
Indicates that one entity is a subsequent or later-occurring instance of the same type or pattern as another entity.
-
D.
isSuccessorTo
Indicates that one entity directly follows another in an ordered sequence, coming immediately after it.
-
E.
locatedInTimeBefore
Indicates that one temporal event or interval occurs entirely before another in time.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a2404c819090cb0825a67a64fa |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.