Triple

T30307833
Position Surface form Disambiguated ID Type / Status
Subject East 63rd Street E770837 entity
Predicate hasNearbyLandmark P2064 FINISHED
Object Central Park
Central Park is a large, iconic urban park in the heart of Manhattan, New York City, known for its expansive green spaces, recreational facilities, and cultural landmarks.
E5448 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: Central Park | Statement: [East 63rd Street, hasNearbyLandmark, Central 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: Central Park
Triple: [East 63rd Street, hasNearbyLandmark, Central Park]
Generated description
Central Park is a large, iconic urban park in the heart of Manhattan, New York City, known for its expansive green spaces, recreational facilities, and cultural landmarks.

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_69f22488f224819081b0f3ec41ab975c completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6816966e8819094d81abb060be372 completed May 2, 2026, 10:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a27989d5fd0819097aab24fa5d9ce33 completed June 9, 2026, 4:37 a.m.
NEDg Description generation batch_6a279b4477108190b3c2d60ab9ac5c15 completed June 9, 2026, 4:49 a.m.
NED2 Entity disambiguation (via description) batch_6a279ba7ee108190b856c41db2cc4b7e completed June 9, 2026, 4:50 a.m.
Created at: April 29, 2026, 7:49 p.m.