Triple
T29339522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast of Saint Luke |
E743998
|
entity |
| Predicate | hasPatronageAspect |
P45407
|
FINISHED |
| Object | physicians |
—
|
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: physicians | Statement: [Feast of Saint Luke, hasPatronageAspect, physicians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatronageAspect Context triple: [Feast of Saint Luke, hasPatronageAspect, physicians]
-
A.
hasPatronageOver
chosen
Indicates that one entity serves as a patron, sponsor, or protector for another, exercising support, guidance, or authority over it.
-
B.
hasPatronageContext
Indicates that one entity is involved with or characterized by a particular patronage relationship, setting, or circumstances.
-
C.
hasPartInHisPatronage
Indicates that one entity is included or involved as a component, beneficiary, or participant within another entity’s sphere of patronage or sponsorship.
-
D.
hasNotablePatron
Indicates that an entity is significantly supported, sponsored, or championed by a distinguished or influential patron.
-
E.
hasImperialPatronage
Indicates that an entity receives official support, sponsorship, or protection from an imperial authority.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 28, 2026, 1:33 p.m.