Triple

T11818548
Position Surface form Disambiguated ID Type / Status
Subject Colorado Scenic and Historic Byways system E281064 entity
Predicate hasDesignationCriteria P101662 FINISHED
Object scenic significance 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: scenic significance | Statement: [Colorado Scenic and Historic Byways system, hasDesignationCriteria, scenic significance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDesignationCriteria
Context triple: [Colorado Scenic and Historic Byways system, hasDesignationCriteria, scenic significance]
  • A. hasDesignation
    Indicates that an entity holds or is assigned a specific title, label, or formal designation.
  • B. hasDesignationBy
    Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
  • C. hasDesignationForm
    Indicates that an entity is associated with a particular form or format used for its designation or naming.
  • D. canBeDesignatedBy
    Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
  • E. hasCriticalDesignation
    Indicates that an entity has been assigned a status or label marking it as critical in importance, priority, or required attention.
  • 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_69d6ab26aae88190b2489efcb2a24234 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a5e760988190b50d13bba5ef5b43 completed April 10, 2026, 7:25 a.m.
PD Predicate disambiguation batch_69d8a251fc08819095933f1d13c3b742 completed April 10, 2026, 7:10 a.m.
PDg Predicate description generation batch_69d8a43cc0c881909fed7cd759fe90b1 completed April 10, 2026, 7:18 a.m.
Created at: April 8, 2026, 9:42 p.m.