Triple
T24289250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Cathan |
E605765
|
entity |
| Predicate | feastDayStatus |
P155711
|
FINISHED |
| Object | locally observed only |
—
|
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: locally observed only | Statement: [Saint Cathan, feastDayStatus, locally observed only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feastDayStatus Context triple: [Saint Cathan, feastDayStatus, locally observed only]
-
A.
feastDayObservedOn
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
-
B.
feastDayHonors
Indicates that a particular feast day is dedicated to honoring or commemorating a specific person, group, or event.
-
C.
hasFeastOrCommemoration
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
D.
institutedFeast
Indicates that an authority or group formally established and put into practice a particular feast or festival as an ongoing observance.
-
E.
sharesFeastDayWith
Indicates that two entities are commemorated or celebrated on the same feast day in a liturgical or religious calendar.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5908e08190a9f150df924a7160 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 18, 2026, 12:08 a.m.