Triple

T34610731
Position Surface form Disambiguated ID Type / Status
Subject Moika River embankment bridges E888723 entity
Predicate hasPart P35 FINISHED
Object Postoffice Bridge
Postoffice Bridge is a small historic pedestrian suspension bridge in Saint Petersburg, Russia, spanning the Moika River near the city’s central post office.
E2248021 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: Postoffice Bridge | Statement: [Moika River embankment bridges, hasPart, Postoffice Bridge]
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: Postoffice Bridge
Triple: [Moika River embankment bridges, hasPart, Postoffice Bridge]
Generated description
Postoffice Bridge is a small historic pedestrian suspension bridge in Saint Petersburg, Russia, spanning the Moika River near the city’s central post office.

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_69f349d584e08190b40b9f6281ad50c4 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f721c63e9481908635d354b164c4db completed May 3, 2026, 10:21 a.m.
NED1 Entity disambiguation (via context triple) batch_6a410ca19af8819098920534d9cd2d8c completed June 28, 2026, 11:59 a.m.
NEDg Description generation batch_6a410d5215e88190b53f93c0bfc61bfd completed June 28, 2026, 12:02 p.m.
NED2 Entity disambiguation (via description) batch_6a410e09a0d48190aae6deab051064a3 completed June 28, 2026, 12:05 p.m.
Created at: May 1, 2026, 2:03 a.m.