Triple
T12751481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolomyazhsky Bridge |
E304742
|
entity |
| Predicate | isInWaterBodyBasin |
P18951
|
FINISHED |
| Object | Neva River basin |
—
|
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: Neva River basin | Statement: [Kolomyazhsky Bridge, isInWaterBodyBasin, Neva River basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInWaterBodyBasin Context triple: [Kolomyazhsky Bridge, isInWaterBodyBasin, Neva River basin]
-
A.
locatedInBasin
chosen
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
-
B.
isInlandWaterBodyOf
Indicates that one water body is an inland (non-oceanic) water feature that is geographically part of, contained within, or associated with another entity.
-
C.
inWaterBodyRegion
Indicates that an entity is located within a specific region or area of a water body.
-
D.
locatedInWaterBodyType
Indicates that an entity is situated within or on a body of water of a specified type (e.g., lake, river, ocean).
-
E.
appliesToWaterBody
Indicates that something (such as a rule, condition, property, or effect) is relevant or applicable specifically to a particular water body.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.