Triple

T2483956
Position Surface form Disambiguated ID Type / Status
Subject Devils Postpile National Monument E55881 entity
Predicate accessManagedBy P40308 FINISHED
Object mandatory shuttle bus in peak season 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: mandatory shuttle bus in peak season | Statement: [Devils Postpile National Monument, accessManagedBy, mandatory shuttle bus in peak season]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: accessManagedBy
Context triple: [Devils Postpile National Monument, accessManagedBy, mandatory shuttle bus in peak season]
  • A. accessRole
    Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
  • B. managedIn
    Indicates that one entity is administered, operated, or overseen within the scope, control, or jurisdiction of another entity.
  • C. accessStatus
    Indicates the current level or state of permission or availability for accessing a resource or entity.
  • D. accessRestrictedTo
    Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
  • E. hasManagement
    Indicates that one entity exercises managerial authority or oversight over another entity.
  • F. None of above. chosen

Provenance (4 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_69ab49e670a88190b928e08302381710 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abd20b6d008190acec0eb172e218c9 completed March 7, 2026, 7:21 a.m.
PD Predicate disambiguation batch_69abd0b7cf088190bcff4dac6150044c completed March 7, 2026, 7:16 a.m.
PDg Predicate description generation batch_69abd209d934819093600889af9104c3 completed March 7, 2026, 7:21 a.m.
Created at: March 6, 2026, 9:45 p.m.