Triple
T22769959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zwardoń–Skalité rail crossing |
E563526
|
entity |
| Predicate | mountainPassRegion |
P24755
|
FINISHED |
| Object | Silesian Beskids mountain passes |
—
|
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: Silesian Beskids mountain passes | Statement: [Zwardoń–Skalité rail crossing, mountainPassRegion, Silesian Beskids mountain passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainPassRegion Context triple: [Zwardoń–Skalité rail crossing, mountainPassRegion, Silesian Beskids mountain passes]
-
A.
controlledMountainPasses
Indicates that an entity had authority over and could regulate access through specific mountain passes.
-
B.
mountainPassType
Indicates the specific classification or category of a mountain pass based on its characteristics or use.
-
C.
locatedInMountainRangeRegion
chosen
Indicates that a place or geographic entity is situated within the area covered by a specific mountain range.
-
D.
sacredMountainRegion
Indicates a region that is recognized or designated as a sacred mountain area.
-
E.
hasMountainPassNearby
Indicates that a mountain pass is located in close proximity to the referenced place or feature.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b5cea44819097290351da9c488d |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:27 p.m.