Triple

T35863683
Position Surface form Disambiguated ID Type / Status
Subject Mount Norikura E1037021 entity
Predicate hasSeasonalAccessRestrictions P177844 FINISHED
Object true 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: true | Statement: [Mount Norikura, hasSeasonalAccessRestrictions, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSeasonalAccessRestrictions
Context triple: [Mount Norikura, hasSeasonalAccessRestrictions, true]
  • A. hasSeasonalStatus
    Indicates that an entity’s status, availability, or condition varies according to a particular season or time of year.
  • B. restrictedBySeason chosen
    Indicates that the applicability or availability of something is limited or controlled based on a specific time of year or season.
  • C. hasSeasonalOffering
    Indicates that an entity provides or features a special offering that is available only during a particular season or time of year.
  • D. hasPublicAccessRestrictions
    Indicates that there are specific limitations or conditions governing public access to the associated resource or entity.
  • E. seasonalValidity
    Indicates that something is valid, applicable, or in effect only during a specific season or set of seasons.
  • 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_69f76e1d279c8190843e5b64a0a12c3f completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_6a002e71bdc48190b922f2d3b362d259 completed May 10, 2026, 7:06 a.m.
PD Predicate disambiguation batch_6a002e1a28708190b65f9e657c770bab completed May 10, 2026, 7:04 a.m.
Created at: May 3, 2026, 4:06 p.m.