Triple

T2137818
Position Surface form Disambiguated ID Type / Status
Subject Routeburn Track E46694 entity
Predicate requiresBooking P19288 FINISHED
Object Great Walk huts 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: Great Walk huts | Statement: [Routeburn Track, requiresBooking, Great Walk huts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresBooking
Context triple: [Routeburn Track, requiresBooking, Great Walk huts]
  • A. bookingRequirement chosen
    Indicates that a particular condition, rule, or prerequisite must be satisfied in order to make or confirm a booking.
  • B. requiresCheckIn
    Indicates that one entity must perform a check-in action or be checked in as a prerequisite for another entity, event, or process to proceed.
  • C. bookingOption
    Indicates a selectable arrangement or choice available for making a booking, such as a specific time, package, or set of conditions under which a reservation can be made.
  • D. requiresForHeadAppointment
    Indicates that a certain condition, qualification, or prior role must be fulfilled in order for an entity to be appointed as the head of something.
  • E. requiresCheckOut
    Indicates that one entity must be formally checked out or borrowed before it can be used, accessed, or taken by another entity.
  • 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_69a88a174ab48190a5db20c132e5dccf completed March 4, 2026, 7:37 p.m.
NER Named-entity recognition batch_69abbf74147c81908793c3694894f94a completed March 7, 2026, 6:02 a.m.
PD Predicate disambiguation batch_69abbd96a3b0819081efbfef975e1513 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:44 p.m.