Triple

T918758
Position Surface form Disambiguated ID Type / Status
Subject Skyfari aerial tram E19832 entity
Predicate ticketRequirement P5937 FINISHED
Object zoo admission required 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: zoo admission required | Statement: [Skyfari aerial tram, ticketRequirement, zoo admission required]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ticketRequirement
Context triple: [Skyfari aerial tram, ticketRequirement, zoo admission required]
  • A. hasTicketRequirement chosen
    Indicates that an entity is subject to a specific ticket or admission requirement in order for access, participation, or use to be allowed.
  • B. visitorRequirement
    Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
  • C. bookingRequirement
    Indicates that a particular condition, rule, or prerequisite must be satisfied in order to make or confirm a booking.
  • D. membershipRequired
    Indicates that access to or use of something is conditional on being a member of a specified group or organization.
  • E. dialogRequirement
    Indicates that a certain condition, piece of information, or interaction must occur within a dialog or conversation for a related action, state, or process to proceed or be considered valid.
  • 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_69a493a099788190a696d9d8408cbaf4 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b388f0bc8190a087222636135ba5 completed March 1, 2026, 9:45 p.m.
PD Predicate disambiguation batch_69a4b2944ff88190a260be5355132ba5 completed March 1, 2026, 9:41 p.m.
Created at: March 1, 2026, 7:40 p.m.