Triple

T31016863
Position Surface form Disambiguated ID Type / Status
Subject Dahlonega gold mining district E790345 entity
Predicate approximateCoordinateRegion P10760 FINISHED
Object 34.5°N 84.0°W 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: 34.5°N 84.0°W | Statement: [Dahlonega gold mining district, approximateCoordinateRegion, 34.5°N 84.0°W]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: approximateCoordinateRegion
Context triple: [Dahlonega gold mining district, approximateCoordinateRegion, 34.5°N 84.0°W]
  • A. approximationRegion
    Indicates a region or range within which a value, object, or condition is considered an acceptable approximation of a reference or target.
  • B. hasApproximateCoordinates chosen
    Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
  • C. coordinateRegion
    Indicates that one region is geographically or spatially aligned with, or corresponds to, another region within a shared coordinate framework.
  • D. coordinateRegionWith
    Indicates that one entity aligns or harmonizes its regional scope, boundaries, or parameters with those of another entity.
  • E. regionCorrespondsRoughlyTo
    Indicates that one region approximately matches or aligns with another in location, extent, or boundaries, but not with precise or exact correspondence.
  • 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_69f224c811508190a7de096a5b1f5798 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe189fec148190aeef51b417ba15b0 completed May 8, 2026, 5:08 p.m.
PD Predicate disambiguation batch_69fe17285b0881908de7569d8dbd20bd completed May 8, 2026, 5:02 p.m.
Created at: April 29, 2026, 8:58 p.m.