Triple

T27826777
Position Surface form Disambiguated ID Type / Status
Subject Milford, Delaware E702976 entity
Predicate hasPark P105 FINISHED
Object Bicentennial Park
Bicentennial Park is a public recreational green space located in Milford, Delaware, offering outdoor amenities and community gathering areas for residents and visitors.
E1798518 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: Bicentennial Park | Statement: [Milford, Delaware, hasPark, Bicentennial Park]
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: Bicentennial Park
Triple: [Milford, Delaware, hasPark, Bicentennial Park]
Generated description
Bicentennial Park is a public recreational green space located in Milford, Delaware, offering outdoor amenities and community gathering areas for residents and visitors.

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_69ef840ad1e88190b5bff2d1ddec8700 completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69f6389747288190b9aad922c5fff6be completed May 2, 2026, 5:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15b87c46788190ad9d659ad8d18def completed May 26, 2026, 3:13 p.m.
NEDg Description generation batch_6a15b9ad99608190b443328957d10875 completed May 26, 2026, 3:18 p.m.
NED2 Entity disambiguation (via description) batch_6a15ba8179108190b060c242c29f34bc completed May 26, 2026, 3:21 p.m.
Created at: April 27, 2026, 5:52 p.m.