Triple
T34950583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terespol–Brest |
E1007979
|
entity |
| Predicate | hasNearbyRiverPort |
P131377
|
FINISHED |
| Object | Brest river facilities |
—
|
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: Brest river facilities | Statement: [Terespol–Brest, hasNearbyRiverPort, Brest river facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyRiverPort Context triple: [Terespol–Brest, hasNearbyRiverPort, Brest river facilities]
-
A.
hasNearbyRiverStructure
Indicates that a river-related structure (such as a dam, bridge, or levee) is located close to the referenced entity.
-
B.
hasRiverPortPotential
Indicates that a location has suitable conditions to support the development or operation of a river port.
-
C.
hasNotableRiverPort
chosen
Indicates that a place possesses a river port recognized for its significance in transport, trade, or regional importance.
-
D.
connectsToRiverPort
Indicates that one location, route, or infrastructure element has a direct linkage or access to a river port.
-
E.
hasTownOnRiver
Indicates that a town is situated on or directly adjacent to a particular river.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4 p.m.