Triple
T14170249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Lister |
E351185
|
entity |
| Predicate | hasClimbingInterest |
P113091
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mount Lister, hasClimbingInterest, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingInterest Context triple: [Mount Lister, hasClimbingInterest, yes]
-
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.
hasRockClimbingPotential
Indicates that an entity possesses suitable characteristics or conditions for successful or promising rock climbing activities.
-
C.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
D.
hasClimbingEthic
Indicates that an entity adheres to or is characterized by a particular set of principles or norms governing climbing behavior or practices.
-
E.
climbingPopularity
Indicates how widely practiced, favored, or in-demand a particular form of climbing or climbing-related activity is among participants.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b472288190b4a271daa54aa6cd |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:01 a.m.