Triple
T37819886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yosemite Decimal System |
E942879
|
entity |
| Predicate | class5Uses |
P184459
|
FINISHED |
| Object | technical rock 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: technical rock climbing | Statement: [Yosemite Decimal System, class5Uses, technical rock climbing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: class5Uses Context triple: [Yosemite Decimal System, class5Uses, technical rock climbing]
-
A.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
-
B.
classificationUsedBy
Indicates that a particular classification system or scheme is employed or applied by a given entity.
-
C.
classificationUsedIn
chosen
Indicates that a particular classification scheme or category is applied or referenced within a given context, system, or resource.
-
D.
class5Description
Indicates that an entity is associated with or characterized by a specific description for its fifth classification level.
-
E.
usedByClass
Indicates that something (such as a resource, method, or component) is utilized or depended upon by a particular class.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:19 p.m.