Triple
T9464140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbe Tunnel (Hamburg) |
E228225
|
entity |
| Predicate | underpasses |
P64005
|
FINISHED |
| Object | Elbe riverbed |
—
|
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: Elbe riverbed | Statement: [Elbe Tunnel (Hamburg), underpasses, Elbe riverbed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underpasses Context triple: [Elbe Tunnel (Hamburg), underpasses, Elbe riverbed]
-
A.
hasBridgeUnderpasses
Indicates that one structure, typically a bridge, includes or provides underpasses that allow passage beneath it.
-
B.
hasUnderpass
Indicates that one location or structure includes or is connected by an underpass beneath another feature or pathway.
-
C.
tunnels
chosen
Indicates that one entity passes through, under, or within another entity via a tunnel-like passage or structure.
-
D.
subterranean
Indicates that one entity is located beneath the surface of the ground or under another structure or area.
-
E.
hasRailwayTunnel
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcec2d88190b93b6e4d881c85c6 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.