Triple
T14616884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Długi Giewont |
E343108
|
entity |
| Predicate | hasClimbingConditions |
P115063
|
FINISHED |
| Object | alpine character typical of the Tatras |
—
|
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: alpine character typical of the Tatras | Statement: [Długi Giewont, hasClimbingConditions, alpine character typical of the Tatras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingConditions Context triple: [Długi Giewont, hasClimbingConditions, alpine character typical of the Tatras]
-
A.
hasClimbingHazard
Indicates that something presents a risk or danger specifically associated with climbing activities.
-
B.
climbingAllowed
Indicates that an entity is permitted to climb onto or up another entity or surface.
-
C.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
D.
canBeClimbedIn
Indicates that one entity is suitable or possible to climb while being inside or within another entity.
-
E.
climbingAccess
Indicates that one entity provides permission, routes, or means for another entity to engage in climbing activities at a particular location or structure.
- F. None of above. chosen
Provenance (4 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46439b88190a4affcc7ccedab6b |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:25 a.m.