Triple
T9350870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Petersburg Dam |
E225013
|
entity |
| Predicate | hasTunnelUnder |
P21069
|
FINISHED |
| Object | main navigation channel |
—
|
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: main navigation channel | Statement: [Saint Petersburg Dam, hasTunnelUnder, main navigation channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTunnelUnder Context triple: [Saint Petersburg Dam, hasTunnelUnder, main navigation channel]
-
A.
hasTunnel
chosen
Indicates that one entity possesses, contains, or is connected by a tunnel to another entity.
-
B.
hasTunnelShape
Indicates that something possesses a form or configuration resembling a tunnel, typically elongated, enclosed, and passage-like.
-
C.
isInTunnelSystem
Indicates that one entity is located within or forms part of a tunnel system associated with another entity.
-
D.
hasRailwayTunnel
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
-
E.
hasSummitTunnel
Indicates that a summit or peak contains or is traversed by a tunnel.
- 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_69ca842abfd48190949d71c3b86eeba8 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f9248c08190a7bb40feec2eb217 |
completed | April 1, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:41 p.m.