Triple
T37819885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yosemite Decimal System |
E942879
|
entity |
| Predicate | class5Subdivision |
P81901
|
FINISHED |
| Object | 5.0–5.15 difficulty scale |
—
|
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: 5.0–5.15 difficulty scale | Statement: [Yosemite Decimal System, class5Subdivision, 5.0–5.15 difficulty scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: class5Subdivision Context triple: [Yosemite Decimal System, class5Subdivision, 5.0–5.15 difficulty scale]
-
A.
collectionSubdivision
Indicates that one collection is a constituent part, section, or subdivision of a larger collection.
-
B.
categorySubdivision
chosen
Indicates that one category functions as a subdivision or subcategory within another broader category.
-
C.
traditionalSubdivisionOf
Indicates that one entity is a historically or culturally recognized sub-unit or component region of another, according to traditional (rather than strictly modern administrative) divisions.
-
D.
subdivisionOfJurisdiction
Indicates that one jurisdiction is a smaller administrative or territorial unit that forms part of a larger jurisdiction.
-
E.
subdivisionAlternativeName
Indicates an alternative or variant name used to refer to a particular subdivision.
- 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_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 3, 2026, 4:19 p.m.