Triple
T7108147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter and Paul Fast |
E165641
|
entity |
| Predicate | feastDateInGregorianCalendar |
P27473
|
FINISHED |
| Object | June 29 |
—
|
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: June 29 | Statement: [Peter and Paul Fast, feastDateInGregorianCalendar, June 29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feastDateInGregorianCalendar Context triple: [Peter and Paul Fast, feastDateInGregorianCalendar, June 29]
-
A.
definesFeastDate
Indicates that one entity specifies or determines the calendar date on which a particular feast or festival is observed.
-
B.
feastDayObservedOn
chosen
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
-
C.
hasFeastOrCommemoration
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
D.
hasDateInGregorianCalendar
Indicates that an entity is associated with a specific date expressed using the Gregorian calendar system.
-
E.
hasAssociatedFeast
Indicates that something (such as a person, event, or entity) is linked to a specific feast or celebratory religious observance.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5bbd4e481909e0948d01c6b15f4 |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:42 p.m.