Triple
T31891179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sancho Ramírez of Aragon |
E814149
|
entity |
| Predicate | replacedRite |
P116537
|
FINISHED |
| Object | Mozarabic liturgy |
—
|
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: Mozarabic liturgy | Statement: [Sancho Ramírez of Aragon, replacedRite, Mozarabic liturgy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedRite Context triple: [Sancho Ramírez of Aragon, replacedRite, Mozarabic liturgy]
-
A.
replacedReligiousRitesOf
chosen
Indicates that one set of religious rites or practices has been superseded or taken the place of another.
-
B.
replacedStandard
Indicates that one standard has been superseded or taken the place of another standard.
-
C.
liturgicalSubstitute
Indicates that one liturgical element, person, or text is used in place of another within a religious rite or ceremony.
-
D.
replacedInReform
Indicates that one entity was substituted or superseded by another as part of a formal reform or restructuring process.
-
E.
ordinationRite
Indicates the formal religious ceremony or ritual through which a person is conferred an office or ordained to a specific role.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 30, 2026, 11:58 p.m.