Triple

T26317137
Position Surface form Disambiguated ID Type / Status
Subject Druid Hills E662001 entity
Predicate hasNotablePark P642 FINISHED
Object Deepdene Park
Deepdene Park is a historic woodland park and nature preserve in the Druid Hills area of Atlanta, known for its trails, ravines, and part in the Olmsted-designed linear park system.
E2092500 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: Deepdene Park | Statement: [Druid Hills, hasNotablePark, Deepdene 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: Deepdene Park
Triple: [Druid Hills, hasNotablePark, Deepdene Park]
Generated description
Deepdene Park is a historic woodland park and nature preserve in the Druid Hills area of Atlanta, known for its trails, ravines, and part in the Olmsted-designed linear park system.

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_69ee812e73048190aae587f1d51e5a06 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f60f27fc6c8190b221b4a3b677d0c3 completed May 2, 2026, 2:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3704765f208190a18f228355529365 completed June 20, 2026, 9:21 p.m.
NEDg Description generation batch_6a370577d8e08190848ce63a9865793d completed June 20, 2026, 9:26 p.m.
NED2 Entity disambiguation (via description) batch_6a37061b69fc81908c02244b45d74771 completed June 20, 2026, 9:28 p.m.
Created at: April 26, 2026, 10:25 p.m.