Triple
T33017205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wonderworking icon of St. Nicholas |
E844808
|
entity |
| Predicate | associatedSaintVirtue |
P206319
|
FINISHED |
| Object | charity |
—
|
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: charity | Statement: [wonderworking icon of St. Nicholas, associatedSaintVirtue, charity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSaintVirtue Context triple: [wonderworking icon of St. Nicholas, associatedSaintVirtue, charity]
-
A.
associatedSaintOccupation
Indicates the occupation or role that is linked to or held by a particular saint.
-
B.
virtuePersonifiedBy
Indicates that an abstract virtue is represented or embodied as a specific person or character.
-
C.
virtuePraisedFor
Indicates that a particular virtue is being commended, admired, or spoken of approvingly by someone.
-
D.
portraysAsSaint
Indicates that one entity depicts or represents another entity as a saintly, holy, or morally exemplary figure.
-
E.
saintPatronageAssociatedWith
Indicates that a patronage relationship exists, where a saint is recognized as a special protector or advocate for a particular person, group, place, activity, or cause.
- F. None of above. chosen
Provenance (4 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:23 a.m.