Triple
T3450500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vincentian Fathers |
E72780
|
entity |
| Predicate | hasFounderFeastDay |
P27473
|
FINISHED |
| Object | 27 September |
—
|
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: 27 September | Statement: [Vincentian Fathers, hasFounderFeastDay, 27 September]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFounderFeastDay Context triple: [Vincentian Fathers, hasFounderFeastDay, 27 September]
-
A.
hasAssociatedFeast
Indicates that something (such as a person, event, or entity) is linked to a specific feast or celebratory religious observance.
-
B.
hasFeastOrCommemoration
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
C.
feastDayObservedOn
chosen
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
-
D.
coFeastDayWith
Indicates that two or more entities share the same feast day or are commemorated liturgically on the same calendar date.
-
E.
isCelebratedIn
Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
- 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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba7324508190b07943cec3ecdb59 |
completed | March 8, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.