Triple
T19889049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast of Saint Mary Magdalene |
E477979
|
entity |
| Predicate | patronageLinkedTo |
P56144
|
FINISHED |
| Object | penitents |
—
|
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: penitents | Statement: [Feast of Saint Mary Magdalene, patronageLinkedTo, penitents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronageLinkedTo Context triple: [Feast of Saint Mary Magdalene, patronageLinkedTo, penitents]
-
A.
patronageFrom
Indicates a relationship where support, sponsorship, or backing is provided to someone or something by a patron.
-
B.
patronage
Indicates a relationship where one party supports, sponsors, or protects another, often in exchange for loyalty, services, or influence.
-
C.
patronageFocus
chosen
Indicates the primary area, subject, or domain that is the focus of an entity’s support, sponsorship, or patronage.
-
D.
sharesPatronageWith
Indicates that two entities are supported, sponsored, or funded by the same patron or sponsoring party.
-
E.
hasPatronageOver
Indicates that one entity serves as a patron, sponsor, or protector for another, exercising support, guidance, or authority over it.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590c1b9c8190abbfaa04b80713b3 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.