Triple

T25664799
Position Surface form Disambiguated ID Type / Status
Subject Tsar Osvoboditel Boulevard, Sofia E643481 entity
Predicate connectsTo P845 FINISHED
Object Eagles' Bridge
Eagles' Bridge is a historic landmark bridge in central Sofia, Bulgaria, known as a key traffic junction and symbolic entrance to the city center.
E1747907 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: Eagles' Bridge | Statement: [Tsar Osvoboditel Boulevard, Sofia, connectsTo, Eagles' 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: Eagles' Bridge
Triple: [Tsar Osvoboditel Boulevard, Sofia, connectsTo, Eagles' Bridge]
Generated description
Eagles' Bridge is a historic landmark bridge in central Sofia, Bulgaria, known as a key traffic junction and symbolic entrance to the city center.

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_69e77e7e45648190a068ed3faa8016ea completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f5faf1f9c48190ad732234e836b143 completed May 2, 2026, 1:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a121e6b0cdc81908826e1d5c0a4742f completed May 23, 2026, 9:38 p.m.
NEDg Description generation batch_6a121fa58ae08190b70faa7e3c81eae8 completed May 23, 2026, 9:44 p.m.
NED2 Entity disambiguation (via description) batch_6a1220284ddc819085b3ca2cad3fbfa9 completed May 23, 2026, 9:46 p.m.
Created at: April 21, 2026, 7:01 p.m.