Triple
T32444485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thame |
E829104
|
entity |
| Predicate | hasMonasticFestival |
P3113
|
FINISHED |
| Object | Buddhist religious festivals |
—
|
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: Buddhist religious festivals | Statement: [Thame, hasMonasticFestival, Buddhist religious festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticFestival Context triple: [Thame, hasMonasticFestival, Buddhist religious festivals]
-
A.
hasPilgrimageOrFeast
Indicates that there is a religious pilgrimage or feast associated with, dedicated to, or occurring in relation to the referenced entity.
-
B.
hasFestivalPeriod
Indicates that there is a specific time period during which a festival or celebratory event takes place.
-
C.
hasFeastOrCommemoration
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
D.
hasRitualDay
Indicates that a specific day is designated or associated as the ritual or ceremonial day for an entity.
-
E.
hasFestival
chosen
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: May 1, 2026, 12:55 a.m.