Triple
T15975683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordenskjöld Peak |
E387437
|
entity |
| Predicate | hasClimbing |
P35393
|
FINISHED |
| Object | mountaineering |
—
|
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: mountaineering | Statement: [Nordenskjöld Peak, hasClimbing, mountaineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbing Context triple: [Nordenskjöld Peak, hasClimbing, mountaineering]
-
A.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
-
B.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
C.
climbingActivity
chosen
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
D.
hasClimbingInterest
Indicates that an entity has an interest in or enthusiasm for climbing activities.
-
E.
hasClimbingConditions
Indicates that specific environmental or situational conditions suitable for climbing are present or associated with something.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.