Triple
T25978285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Błędne Skały |
E645999
|
entity |
| Predicate | nearbyTrailNetwork |
P61270
|
FINISHED |
| Object | trails connecting to Szczeliniec Wielki area |
—
|
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: trails connecting to Szczeliniec Wielki area | Statement: [Błędne Skały, nearbyTrailNetwork, trails connecting to Szczeliniec Wielki area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyTrailNetwork Context triple: [Błędne Skały, nearbyTrailNetwork, trails connecting to Szczeliniec Wielki area]
-
A.
hasNearbyTrailheadFor
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
B.
hikingTrailPassesNear
Indicates that a hiking trail runs close to, but does not directly intersect or pass through, a specified location or feature.
-
C.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
-
D.
nearbyCampground
Indicates that one location has a campground situated close to it in geographic proximity.
-
E.
nearbyLocation
chosen
Indicates that one location is situated close to another location in physical space.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 22, 2026, 8:52 a.m.