Triple

T37683998
Position Surface form Disambiguated ID Type / Status
Subject Short Creek community E938314 entity
Predicate mainSettlementIn P13187 FINISHED
Object Colorado City, Arizona NE NERFINISHED

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: Colorado City, Arizona | Statement: [Short Creek community, mainSettlementIn, Colorado City, Arizona]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mainSettlementIn
Context triple: [Short Creek community, mainSettlementIn, Colorado City, Arizona]
  • A. mainSettlement chosen
    Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
  • B. mainTownOn
    Indicates that one town is the primary or principal town located on or associated with a particular geographic feature, route, or area.
  • C. mainSettlementLocatedOn
    Indicates that the primary settlement of an area is situated on or directly adjacent to a specified geographic feature or location.
  • D. formerMainSettlement
    Indicates that a location was previously the primary or most important settlement of a given area, but no longer holds that status.
  • E. primarySettlementOrigin
    Indicates that one settlement is the main or original source from which another settlement was founded or developed.
  • 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_69f76ed881408190bc62a969530a4a53 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbb084760c8190a1554985d3c3cb7a completed May 6, 2026, 9:20 p.m.
PD Predicate disambiguation batch_69fbadf3cb548190ba3b7514f76b790a completed May 6, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:18 p.m.