Triple

T32044084
Position Surface form Disambiguated ID Type / Status
Subject Hilltop, Minnesota E818290 entity
Predicate hasFireServicesContractedFrom P62810 FINISHED
Object Columbia Heights, Minnesota 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: Columbia Heights, Minnesota | Statement: [Hilltop, Minnesota, hasFireServicesContractedFrom, Columbia Heights, Minnesota]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFireServicesContractedFrom
Context triple: [Hilltop, Minnesota, hasFireServicesContractedFrom, Columbia Heights, Minnesota]
  • A. hasFireServicesFrom chosen
    Indicates that one entity receives fire protection or firefighting services from another entity.
  • B. hasFireRescueService
    Indicates that an entity is served by, or responsible for providing, a fire and rescue service.
  • C. hasFireAndRescueServiceCategory
    Indicates the specific fire and rescue service classification or category assigned to an entity, such as a building, facility, or site.
  • D. hasRuralFireServiceBrigade
    Indicates that a specified area or jurisdiction is served by a particular rural fire service brigade.
  • E. hasRescueServices
    Indicates that one entity provides or is equipped with rescue or emergency response services for another entity or area.
  • 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_69f348fcfb648190859f6be5e04b7cfe completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69feb342994081909481ec8ec5d44928 completed May 9, 2026, 4:08 a.m.
PD Predicate disambiguation batch_69feb046e4e48190b96649aa28529cc9 completed May 9, 2026, 3:55 a.m.
Created at: May 1, 2026, 12:19 a.m.