Triple

T31973385
Position Surface form Disambiguated ID Type / Status
Subject Wollumbin E816374 entity
Predicate summitAccessStatus P32027 FINISHED
Object restricted to protect cultural values 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: restricted to protect cultural values | Statement: [Wollumbin, summitAccessStatus, restricted to protect cultural values]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: summitAccessStatus
Context triple: [Wollumbin, summitAccessStatus, restricted to protect cultural values]
  • A. summitStatus
    Indicates the current state or outcome of a summit event, such as whether it is planned, ongoing, completed, or canceled.
  • B. summitAccessInfrastructure
    Indicates the presence or provision of infrastructure that enables access to a summit, such as paths, roads, or transport facilities.
  • C. hasSummitAccess
    Indicates that an entity is permitted or able to reach or enter the summit or highest level of a specified place, system, or structure.
  • D. accessStatus chosen
    Indicates the current level or state of permission or availability for accessing a resource or entity.
  • E. summitAccessibleFrom
    Indicates that a summit can be reached or accessed starting from a specified location or route.
  • 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_69f348f5ae5481909da0247869f51955 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b34303a88190b17cadc63ce00be3 completed May 3, 2026, 2:30 a.m.
PD Predicate disambiguation batch_69f6b151ad008190836c1bcdec503ce2 completed May 3, 2026, 2:22 a.m.
Created at: May 1, 2026, 12:10 a.m.