Triple

T33261428
Position Surface form Disambiguated ID Type / Status
Subject Bercy Park footbridges E851522 entity
Predicate hasAccessTo P1017 FINISHED
Object Bercy Park
Bercy Park is a large urban green space in eastern Paris known for its landscaped gardens, ponds, and pedestrian bridges connecting it to the Seine and surrounding neighborhoods.
E1088777 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: Bercy Park | Statement: [Bercy Park footbridges, hasAccessTo, Bercy 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: Bercy Park
Triple: [Bercy Park footbridges, hasAccessTo, Bercy Park]
Generated description
Bercy Park is a large urban green space in eastern Paris known for its landscaped gardens, ponds, and pedestrian bridges connecting it to the Seine and surrounding neighborhoods.

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_69f349642dac81908a37ffcc3b976a55 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6de1a4dfc81909a4fa85975a54b14 completed May 3, 2026, 5:33 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3543115c80819089170351dd0afe21 completed June 19, 2026, 1:24 p.m.
NEDg Description generation batch_6a354385a7d48190bda1eb1be7f0b387 completed June 19, 2026, 1:26 p.m.
NED2 Entity disambiguation (via description) batch_6a3544cd2b448190aad907008bda0dcb completed June 19, 2026, 1:31 p.m.
Created at: May 1, 2026, 1:31 a.m.