Triple
T23575388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Society of Mary |
E580239
|
entity |
| Predicate | liturgicalFeastRelatedToFounder |
P153234
|
FINISHED |
| Object | January 22 |
—
|
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: January 22 | Statement: [Society of Mary, liturgicalFeastRelatedToFounder, January 22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalFeastRelatedToFounder Context triple: [Society of Mary, liturgicalFeastRelatedToFounder, January 22]
-
A.
founderReligiousOrder
Indicates that a person established or created a particular religious order.
-
B.
hasReligiousFounderAssociated
Indicates that an entity is associated with a specific religious founder, typically through origin, dedication, or foundational influence.
-
C.
associatedPilgrimageFounder
Indicates a relationship where a pilgrimage is linked to the person recognized as its founder or originator.
-
D.
founderOfOrder
Indicates that an entity established or created a particular order, organization, or structured group.
-
E.
liturgicalMemorialEstablishedBy
Indicates that a particular person or authority formally instituted or created a specific liturgical memorial or commemoration.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd5a7e88190ba348d58e552bd3c |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:38 p.m.