Triple
T15250809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxon Switzerland |
E364512
|
entity |
| Predicate | hasClimbingTradition |
P9785
|
FINISHED |
| Object | free climbing |
—
|
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: free climbing | Statement: [Saxon Switzerland, hasClimbingTradition, free climbing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingTradition Context triple: [Saxon Switzerland, hasClimbingTradition, free climbing]
-
A.
climbingHabit
Indicates a relationship where an entity has a tendency or behavior of climbing, such as regularly ascending surfaces, structures, or other objects.
-
B.
hasClimbingInterest
Indicates that an entity has an interest in or enthusiasm for climbing activities.
-
C.
climbingDiscipline
chosen
Indicates the specific style or category of climbing practiced or associated with an entity (e.g., bouldering, sport, trad).
-
D.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
E.
hasClimbingEthic
Indicates that an entity adheres to or is characterized by a particular set of principles or norms governing climbing behavior or practices.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f728648190b2c86e4528542b65 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.