Triple
T30150978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 黄浦江 |
E766392
|
entity |
| Predicate | 跨越隧道 |
P67400
|
FINISHED |
| Object | 外滩隧道 |
—
|
LITERAL 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: 外滩隧道 | Statement: [黄浦江, 跨越隧道, 外滩隧道]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 跨越隧道 Context triple: [黄浦江, 跨越隧道, 外滩隧道]
-
A.
crossedByTunnel
chosen
Indicates that one entity (typically a barrier like a mountain, river, or road) is traversed or passed through by another entity via a tunnel.
-
B.
hasRailwayTunnel
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
-
C.
SeikanTunnelType
Indicates that one entity is classified as a specific type or category of Seikan Tunnel.
-
D.
hasBridgeAndTunnelStructures
Indicates that there exist both bridge and tunnel structures associated with or connecting the related entities.
-
E.
SeikanTunnelConnects
Indicates that the Seikan Tunnel serves as a physical connection between two geographic locations or regions.
- F. None of above.
Provenance (3 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed4297c81909062f19b7795f181 |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.