Triple
T8665104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans Meyer |
E205648
|
entity |
| Predicate | coClimber |
P83963
|
FINISHED |
| Object | Ludwig Purtscheller |
—
|
NE NERFINISHED |
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: Ludwig Purtscheller | Statement: [Hans Meyer, coClimber, Ludwig Purtscheller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coClimber Context triple: [Hans Meyer, coClimber, Ludwig Purtscheller]
-
A.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
B.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
C.
climbingClass
Indicates the difficulty or grade level assigned to a climbing route, problem, or activity.
-
D.
climbingDiscipline
Indicates the specific style or category of climbing practiced or associated with an entity (e.g., bouldering, sport, trad).
-
E.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48a0ae108190b33dadcc3cb18949 |
completed | March 31, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:30 p.m.