Triple

T35574163
Position Surface form Disambiguated ID Type / Status
Subject Radisson Lake E1028026 entity
Predicate hasHumanGeographyAspect P35476 FINISHED
Object historical naming practice 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: historical naming practice | Statement: [Radisson Lake, hasHumanGeographyAspect, historical naming practice]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHumanGeographyAspect
Context triple: [Radisson Lake, hasHumanGeographyAspect, historical naming practice]
  • A. hasGeographyCharacteristic
    Indicates that an entity possesses a specific geographical feature, property, or attribute.
  • B. hasGeographicType
    Indicates that an entity is associated with or classified by a specific type or category of geographic feature or area.
  • C. impliesGeographicalFact
    Indicates that one geographical statement or condition logically entails the truth of another geographical fact.
  • D. geographyBehavior
    Indicates how an entity behaves, functions, or interacts in relation to its geographic context or location.
  • E. geographicalPractice chosen
    Indicates a relationship where an entity engages in or is associated with a practice, activity, or method that is specific to or characteristic of a particular geographic area or location.
  • 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_69f76e0386688190b931bacdc145938c completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79ec355048190af30123ceb6efa2b completed May 3, 2026, 7:15 p.m.
PD Predicate disambiguation batch_69f79e4bdbcc8190be7a0d2cf8a77b64 completed May 3, 2026, 7:13 p.m.
Created at: May 3, 2026, 4:04 p.m.