Triple

T35450321
Position Surface form Disambiguated ID Type / Status
Subject Moskenes Municipality E1024608 entity
Predicate historicallyRegardedAsCentre P145012 FINISHED
Object Reine 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: Reine | Statement: [Moskenes Municipality, historicallyRegardedAsCentre, Reine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyRegardedAsCentre
Context triple: [Moskenes Municipality, historicallyRegardedAsCentre, Reine]
  • A. historicalCenterFor chosen
    Indicates that one entity has served as a central or focal place of historical significance, activity, or development for another entity.
  • B. hasMajorHistoricalCentersIn
    Indicates that an entity possesses significant, historically important centers or hubs located within a specified place or region.
  • C. historicallyImportantCenter
    Indicates that a place has served as a significant focal point of historical events, activities, or influence.
  • D. hasHistoricCenterStatus
    Indicates that an entity has been designated or recognized as a historic center, typically due to its cultural, architectural, or historical significance.
  • E. hasHistoricCenterNearby
    Indicates that one entity is located close to another entity that serves as a historic center or historically significant core 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_69f76df92f108190817222e520e22268 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_6a00b03a50a88190bfb95cdcfc6142a2 completed May 10, 2026, 4:20 p.m.
PD Predicate disambiguation batch_6a00afe55f248190b2cb4c7e62cc3ffc completed May 10, 2026, 4:18 p.m.
Created at: May 3, 2026, 4:04 p.m.