Triple

T4206643
Position Surface form Disambiguated ID Type / Status
Subject Ringerike E93797 entity
Predicate hasTraditionalDistrictStatus P49478 FINISHED
Object yes 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: yes | Statement: [Ringerike, hasTraditionalDistrictStatus, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTraditionalDistrictStatus
Context triple: [Ringerike, hasTraditionalDistrictStatus, yes]
  • A. hasTraditionalCountyStatus
    Indicates that an entity holds the official or customary status of being recognized as a traditional county within a given jurisdiction.
  • B. hasCapitalDistrictStatus
    Indicates that an administrative region holds the official status of being a capital district within a country or larger jurisdiction.
  • C. hasTraditionalCommunity
    Indicates that an entity possesses or is associated with a community that maintains traditional practices, customs, or ways of life.
  • D. traditionalDistrict chosen
    Indicates that an entity is located in, associated with, or belongs to a historically recognized or customary administrative or cultural district.
  • E. containsDistrictMunicipality
    Indicates that an administrative region includes one or more district municipalities within its boundaries.
  • 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_69b3451743608190808f41d17ccf2650 completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b34e098da881909a0cc339cc186627 completed March 12, 2026, 11:36 p.m.
PD Predicate disambiguation batch_69b347efd9b08190bb50f82e4e7fe06d completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:03 p.m.