Triple
T29971427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svitava River |
E761327
|
entity |
| Predicate | hasRailwayAlongValley |
P55241
|
FINISHED |
| Object | Brno–Česká Třebová railway line |
—
|
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: Brno–Česká Třebová railway line | Statement: [Svitava River, hasRailwayAlongValley, Brno–Česká Třebová railway line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailwayAlongValley Context triple: [Svitava River, hasRailwayAlongValley, Brno–Česká Třebová railway line]
-
A.
hasValleyRailLine
chosen
Indicates that a location or region is traversed or served by a railway line running through a valley.
-
B.
gorgeTraversedByRailway
Indicates that a railway line passes through or across the gorge.
-
C.
railwayRunsAlong
Indicates that a railway line extends parallel to and in close proximity with another feature or route for a significant distance.
-
D.
hasMountainRailwayConnectionTo
Indicates that there is a railway line specifically adapted for mountainous terrain that connects one location to another.
-
E.
hasHeadOfValleyNear
Indicates that the head (uppermost part) of a valley is located near a specified reference feature or 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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 29, 2026, 6:32 p.m.