Triple
T37819880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yosemite Decimal System |
E942879
|
entity |
| Predicate | class1Description |
P34982
|
FINISHED |
| Object | easy hiking on a trail |
—
|
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: easy hiking on a trail | Statement: [Yosemite Decimal System, class1Description, easy hiking on a trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: class1Description Context triple: [Yosemite Decimal System, class1Description, easy hiking on a trail]
-
A.
category1Description
chosen
Indicates that something serves as the primary descriptive text or explanation for a first or main category.
-
B.
classificationOf
Indicates that one entity serves as a classification, category, or type under which another entity is grouped or organized.
-
C.
definesClassification
Indicates that one entity specifies or establishes the classification or category to which another entity belongs.
-
D.
depictsClass
Indicates that one entity visually represents or portrays a particular class or category of entities.
-
E.
coreDescription
Indicates that something provides the primary, central, or most essential description of an entity or concept.
- 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_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:19 p.m.