Triple
T36832604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongdingmen Bridge |
E910183
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | bridge in Beijing |
C65602
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: bridge in Beijing Context triple: [Yongdingmen Bridge, instanceOf, bridge in Beijing]
-
A.
bridge in London
A bridge in London is a structural crossing over the River Thames or other waterways in the city, designed to support vehicular, rail, or pedestrian traffic while integrating with the historic and urban landscape.
-
B.
bridge in Budapest
A bridge in Budapest is a structural crossing over the Danube River that connects the city’s Buda and Pest sides, serving both as vital transportation infrastructure and as an iconic architectural landmark.
-
C.
bridge in Copenhagen
A bridge in Copenhagen is a structural crossing—often designed for pedestrians, cyclists, and vehicles—that spans waterways or roads within the city, integrating functional transport with characteristic Danish urban and architectural aesthetics.
-
D.
bridge in Taiwan
A bridge in Taiwan is a structural construction that spans physical obstacles such as rivers, valleys, or roads within Taiwan’s territory to provide transportation routes for vehicles, pedestrians, or railways.
-
E.
bridge in Moscow
A bridge in Moscow is a structural crossing over the Moskva River or other waterways in the city, serving both transportation needs and often acting as an architectural landmark within the urban landscape.
- F. None of above. chosen
Provenance (1 batch)
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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.