Triple
T10408430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai–Chongming–Jiangsu tunnel-bridge |
E245325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-river infrastructure project |
C22181
|
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: cross-river infrastructure project Context triple: [Shanghai–Chongming–Jiangsu tunnel-bridge, instanceOf, cross-river infrastructure project]
-
A.
cross-sea bridge
A cross-sea bridge is a large-scale transportation structure that spans a body of sea water to connect two land areas, enabling the passage of vehicles, trains, or pedestrians across marine environments.
-
B.
infrastructure project
An infrastructure project is a large-scale, organized effort to plan, design, and construct foundational physical systems—such as transportation, utilities, and public facilities—that support a community’s or region’s economic and social activities.
-
C.
river bridge
chosen
A river bridge is a structure built to span a river, providing a stable pathway for vehicles, pedestrians, or rail traffic to cross from one bank to the other.
-
D.
bridge–tunnel complex
A bridge–tunnel complex is an integrated transportation structure that combines bridge spans and underwater tunnels to carry traffic across wide bodies of water or other large obstacles.
-
E.
combined road and rail bridge–tunnel
A combined road and rail bridge–tunnel is a hybrid transportation structure that integrates both bridge and tunnel segments to carry vehicular and rail traffic across or under a geographic obstacle such as a body of water or valley.
- F. None of above.
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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:09 p.m.