Triple
T33855339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Crispin |
E867756
|
entity |
| Predicate | hasFeastSharedWith |
P154228
|
FINISHED |
| Object | Saint Crispinian |
—
|
NE NERFINISHED |
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: Saint Crispinian | Statement: [Saint Crispin, hasFeastSharedWith, Saint Crispinian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeastSharedWith Context triple: [Saint Crispin, hasFeastSharedWith, Saint Crispinian]
-
A.
hasAssociatedFeast
Indicates that something (such as a person, event, or entity) is linked to a specific feast or celebratory religious observance.
-
B.
sharesCuisineWith
Indicates that two entities offer or are associated with the same type or style of cuisine.
-
C.
hasFeastTraditionWith
chosen
Indicates a relationship where two entities share or participate in a customary feast or celebratory meal tradition together.
-
D.
sharesFoodWith
Indicates that one entity gives or divides its food with another entity so that both can eat from it.
-
E.
feastRelatedTo
Indicates a relationship in which one entity is connected or relevant to a feast, such as by association, participation, context, or thematic linkage.
- 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_69f349943ccc8190a3c41a3e0ae46cbf |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:47 a.m.