Triple
T36505059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Joseph's Day |
E899438
|
entity |
| Predicate | patronageAssociated |
P56144
|
FINISHED |
| Object | Universal Church |
—
|
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: Universal Church | Statement: [Saint Joseph's Day, patronageAssociated, Universal Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronageAssociated Context triple: [Saint Joseph's Day, patronageAssociated, Universal Church]
-
A.
patronage
Indicates a relationship where one party supports, sponsors, or protects another, often in exchange for loyalty, services, or influence.
-
B.
patronageFrom
Indicates a relationship where support, sponsorship, or backing is provided to someone or something by a patron.
-
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.
patronageNetwork
Indicates a relationship where support, favors, or resources are exchanged within a hierarchical network of patrons and clients, typically involving mutual obligations and influence.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.