Triple
T3719966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tau cross |
E81614
|
entity |
| Predicate | hasFeastAssociation |
P9516
|
FINISHED |
| Object | Feast of Saint Anthony the Abbot |
—
|
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: Feast of Saint Anthony the Abbot | Statement: [Tau cross, hasFeastAssociation, Feast of Saint Anthony the Abbot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeastAssociation Context triple: [Tau cross, hasFeastAssociation, Feast of Saint Anthony the Abbot]
-
A.
hasAssociatedFeast
chosen
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.
hasObligationOfFestiveMeal
Indicates that an entity is required to participate in or provide a festive meal as a formal obligation.
-
D.
feast
Indicates that an entity participates in or hosts a large, elaborate meal or celebration involving abundant food and communal dining.
-
E.
feastType
Indicates the specific kind or category of feast associated with an event or occasion.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca9b5ca8819094299fffc02606ce |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.