Triple

T11818553
Position Surface form Disambiguated ID Type / Status
Subject Colorado Scenic and Historic Byways system E281064 entity
Predicate includesFeatureTypes P101663 FINISHED
Object mountain landscapes 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: mountain landscapes | Statement: [Colorado Scenic and Historic Byways system, includesFeatureTypes, mountain landscapes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesFeatureTypes
Context triple: [Colorado Scenic and Historic Byways system, includesFeatureTypes, mountain landscapes]
  • A. includesFigureType
    Indicates that one entity contains or encompasses a specific type or category of figure within it.
  • B. supportsType
    Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
  • C. includesProviderType
    Indicates that one entity’s set of provider types contains or covers the provider type associated with another entity.
  • D. isFeatureBased
    Indicates that one entity is derived from, determined by, or constructed using the characteristics or attributes of another entity.
  • E. includesRouteType
    Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
  • 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.