Triple
T25592994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swan Canal |
E641571
|
entity |
| Predicate | locatedOnWaterSystem |
P63896
|
FINISHED |
| Object | Neva River basin |
—
|
NE NERFINISHED |
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: [Swan Canal, locatedOnWaterSystem, Neva River basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnWaterSystem Context triple: [Swan Canal, locatedOnWaterSystem, Neva River basin]
-
A.
locatedOnWaterbody
Indicates that an entity is situated on or directly adjacent to a specified body of water.
-
B.
locatedInWaterBodyType
Indicates that an entity is situated within or on a body of water of a specified type (e.g., lake, river, ocean).
-
C.
isPartOfWaterSystem
Indicates that one entity is a component, segment, or subsystem within a larger water distribution, treatment, or management system.
-
D.
hasPositionInWatercourse
Indicates that one entity occupies a specific location or position within the course of a body of water.
-
E.
isInWaterwaySystem
chosen
Indicates that an entity is part of, contained within, or traverses a particular waterway network or system.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 21, 2026, 4:25 p.m.