Triple

T37153653
Position Surface form Disambiguated ID Type / Status
Subject Grosse Pointe Park, Michigan E920430 entity
Predicate hasRecreationArea P5383 FINISHED
Object Patterson Park
Patterson Park is a public recreational park in Grosse Pointe Park, Michigan, offering outdoor green space and community amenities for local residents.
E2290028 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: Patterson Park | Statement: [Grosse Pointe Park, Michigan, hasRecreationArea, Patterson 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: Patterson Park
Triple: [Grosse Pointe Park, Michigan, hasRecreationArea, Patterson Park]
Generated description
Patterson Park is a public recreational park in Grosse Pointe Park, Michigan, offering outdoor green space and community amenities for local residents.

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_69f76e9f87c08190b4c8f7fafbd8345a completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fb308ec0c48190a57cb4be4c1ab30a completed May 6, 2026, 12:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5b8c22c4808190b378aac178b9f2ba completed July 18, 2026, 2:22 p.m.
NEDg Description generation batch_6a5b8d096adc8190be8736dd9972d63c completed July 18, 2026, 2:26 p.m.
NED2 Entity disambiguation (via description) batch_6a5b8db62af48190888af33af20d355e completed July 18, 2026, 2:29 p.m.
Created at: May 3, 2026, 4:15 p.m.