Triple
T18848550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Mary Major |
E460979
|
entity |
| Predicate | hasPatronageType |
P73174
|
FINISHED |
| Object | Marian patronage |
—
|
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: Marian patronage | Statement: [Saint Mary Major, hasPatronageType, Marian patronage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatronageType Context triple: [Saint Mary Major, hasPatronageType, Marian patronage]
-
A.
hasPatronageOver
Indicates that one entity serves as a patron, sponsor, or protector for another, exercising support, guidance, or authority over it.
-
B.
typeOfPatronage
chosen
Indicates the specific kind or category of support, sponsorship, or backing that one entity provides to another.
-
C.
patronType
Indicates the classification or category of a patron in relation to a service, institution, or resource.
-
D.
hasPatronCharacter
Indicates that one entity serves as a patron, protector, or guiding figure for another entity.
-
E.
hasNotablePatron
Indicates that an entity is significantly supported, sponsored, or championed by a distinguished or influential patron.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8f079b881908759135c5e2619ee |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.