Triple

T27388232
Position Surface form Disambiguated ID Type / Status
Subject Glenmont, Maryland E691442 entity
Predicate hasLandmark P105 FINISHED
Object Glenmont Shopping Center
Glenmont Shopping Center is a local retail plaza serving as a primary commercial hub for the Glenmont neighborhood in Montgomery County, Maryland.
E1769511 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: Glenmont Shopping Center | Statement: [Glenmont, Maryland, hasLandmark, Glenmont Shopping Center]
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: Glenmont Shopping Center
Triple: [Glenmont, Maryland, hasLandmark, Glenmont Shopping Center]
Generated description
Glenmont Shopping Center is a local retail plaza serving as a primary commercial hub for the Glenmont neighborhood in Montgomery County, Maryland.

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_69ef520386788190bc92cfcd97ebb67a completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f62c8d15d48190825465932c36a6c3 completed May 2, 2026, 4:55 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12a7eff6388190b3aff945062ea2fc completed May 24, 2026, 7:25 a.m.
NEDg Description generation batch_6a12a949b620819092007b2ee7e96064 completed May 24, 2026, 7:31 a.m.
NED2 Entity disambiguation (via description) batch_6a12aa9670988190be61c9aaa57b70c9 completed May 24, 2026, 7:36 a.m.
Created at: April 27, 2026, 12:25 p.m.