Triple

T26290713
Position Surface form Disambiguated ID Type / Status
Subject Woodbine Applefest E661261 entity
Predicate typicalSetting P1957 FINISHED
Object downtown Woodbine
Downtown Woodbine is the central commercial and community hub of Woodbine, known for hosting local events and festivals such as the annual Applefest.
E1717660 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: downtown Woodbine | Statement: [Woodbine Applefest, typicalSetting, downtown Woodbine]
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: downtown Woodbine
Triple: [Woodbine Applefest, typicalSetting, downtown Woodbine]
Generated description
Downtown Woodbine is the central commercial and community hub of Woodbine, known for hosting local events and festivals such as the annual Applefest.

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_69ee812bbd448190be4d7478b057990a completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f60e7a94c48190836f70ae063475c2 completed May 2, 2026, 2:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a118fc5c3d88190bb2897b63129b9c7 completed May 23, 2026, 11:30 a.m.
NEDg Description generation batch_6a1190d030f08190a8d942eba20a52c4 completed May 23, 2026, 11:34 a.m.
NED2 Entity disambiguation (via description) batch_6a119145a7008190b6b01851f1ee63ad completed May 23, 2026, 11:36 a.m.
Created at: April 26, 2026, 10:08 p.m.