Triple

T32380140
Position Surface form Disambiguated ID Type / Status
Subject Fletcher Peak (Nevada) E827392 entity
Predicate proximityToUrbanArea P44123 FINISHED
Object within about an hour drive of Las Vegas Strip 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: within about an hour drive of Las Vegas Strip | Statement: [Fletcher Peak (Nevada), proximityToUrbanArea, within about an hour drive of Las Vegas Strip]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: proximityToUrbanArea
Context triple: [Fletcher Peak (Nevada), proximityToUrbanArea, within about an hour drive of Las Vegas Strip]
  • A. hasUrbanProximity chosen
    Indicates that one entity is located near or within easy access to an urban area associated with another entity.
  • B. hasUrbanAreaApprox
    Indicates an approximate measure or estimate of the size or extent of an entity’s urban area.
  • C. isUrbanizedAround
    Indicates that an area or region has developed urban characteristics or infrastructure surrounding a particular location or feature.
  • D. withinUrbanArea
    Indicates that one entity is located inside the spatial boundaries of an urban area associated with another entity.
  • E. connectsToUrbanCenter
    Indicates that one entity has a direct or functional linkage to an urban center, such as through infrastructure, services, or regular interaction.
  • 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_69f349177ddc8190ab0583f05597056b completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c133d2548190bd25b6f347038f63 completed May 3, 2026, 3:29 a.m.
PD Predicate disambiguation batch_69f6ba6eb32c8190bf405b2011fa48f7 completed May 3, 2026, 3:01 a.m.
Created at: May 1, 2026, 12:51 a.m.