Triple

T33661247
Position Surface form Disambiguated ID Type / Status
Subject Rye E862357 entity
Predicate hasEvent P811 FINISHED
Object Rye Bonfire Night
Rye Bonfire Night is an annual autumn celebration in the historic town of Rye, England, featuring a torchlit procession, bonfire, and fireworks as part of the Sussex bonfire tradition.
E2061784 NE 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: Rye Bonfire Night | Statement: [Rye, hasEvent, Rye Bonfire Night]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Rye Bonfire Night
Triple: [Rye, hasEvent, Rye Bonfire Night]
Generated description
Rye Bonfire Night is an annual autumn celebration in the historic town of Rye, England, featuring a torchlit procession, bonfire, and fireworks as part of the Sussex bonfire tradition.

Provenance (5 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_69f34984c4008190bb82f33a7819da64 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6f9f4498081908d965e87ee6fb5cc completed May 3, 2026, 7:32 a.m.
NED1 Entity disambiguation (via context triple) batch_6a362727f5348190a022bc72b82c87f2 completed June 20, 2026, 5:37 a.m.
NEDg Description generation batch_6a3628077de08190af490293002fb49d completed June 20, 2026, 5:41 a.m.
NED2 Entity disambiguation (via description) batch_6a36290731fc81909c4103917af094bb completed June 20, 2026, 5:45 a.m.
Created at: May 1, 2026, 1:42 a.m.