Triple
T12255510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bor |
E292089
|
entity |
| Predicate | hasBridge |
P386
|
FINISHED |
| Object |
Bor Bridge
Bor Bridge is a notable bridge located in or near the town of Bor, serving as an important local transportation crossing and landmark.
|
E989933
|
NE FINISHED |
How this triple was built (4 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: Bor Bridge | Statement: [Bor, hasBridge, Bor Bridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bor Bridge Context triple: [Bor, hasBridge, Bor Bridge]
-
A.
Tumski Bridge
Tumski Bridge is a historic pedestrian bridge in Wrocław, Poland, known for its picturesque views and tradition of lovers attaching padlocks to its railings.
-
B.
Solkan Bridge
Solkan Bridge is a historic stone arch railway bridge in Slovenia, renowned for having the world's longest stone arch span.
-
C.
Torgovy Bridge
Torgovy Bridge is a historic pedestrian bridge spanning the Griboyedov Canal in Saint Petersburg, Russia.
-
D.
Pevchesky Bridge
Pevchesky Bridge is a historic pedestrian bridge in Saint Petersburg, Russia, known for spanning the Griboyedov Canal near the city’s central landmarks.
-
E.
Pevchesky Bridge
Pevchesky Bridge is a historic pedestrian bridge in Saint Petersburg, Russia, known for spanning the Moika River near the city’s central cultural and architectural landmarks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: Bor Bridge Triple: [Bor, hasBridge, Bor Bridge]
Generated description
Bor Bridge is a notable bridge located in or near the town of Bor, serving as an important local transportation crossing and landmark.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Bor Bridge Target entity description: Bor Bridge is a notable bridge located in or near the town of Bor, serving as an important local transportation crossing and landmark.
-
A.
Tumski Bridge
Tumski Bridge is a historic pedestrian bridge in Wrocław, Poland, known for its picturesque views and tradition of lovers attaching padlocks to its railings.
-
B.
Solkan Bridge
Solkan Bridge is a historic stone arch railway bridge in Slovenia, renowned for having the world's longest stone arch span.
-
C.
Torgovy Bridge
Torgovy Bridge is a historic pedestrian bridge spanning the Griboyedov Canal in Saint Petersburg, Russia.
-
D.
Pevchesky Bridge
Pevchesky Bridge is a historic pedestrian bridge in Saint Petersburg, Russia, known for spanning the Griboyedov Canal near the city’s central landmarks.
-
E.
Pevchesky Bridge
Pevchesky Bridge is a historic pedestrian bridge in Saint Petersburg, Russia, known for spanning the Moika River near the city’s central cultural and architectural landmarks.
- F. None of above. chosen
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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cc9dd5081908880061d52351850 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6555ab68881908813e45548281df3 |
completed | May 2, 2026, 7:49 p.m. |
| NEDg | Description generation | batch_69f6566dccc0819085e059c7b0288f6c |
completed | May 2, 2026, 7:54 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f65799ca588190b9f7a07f5c1a842c |
completed | May 2, 2026, 7:59 p.m. |
Created at: April 8, 2026, 9:52 p.m.