Triple

T24898172
Position Surface form Disambiguated ID Type / Status
Subject Melbourne bus network E623200 entity
Predicate includesNightServices P9559 FINISHED
Object yes 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: yes | Statement: [Melbourne bus network, includesNightServices, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesNightServices
Context triple: [Melbourne bus network, includesNightServices, yes]
  • A. nightServiceSubstitute
    Indicates that one entity serves as a replacement or stand-in for another in providing night-time service.
  • B. requiresNighttimeOperation
    Indicates that the action or process can only be carried out, or is intended to be carried out, during nighttime conditions.
  • C. nightService chosen
    Indicates that a service operates or is available during nighttime hours.
  • D. servedByAtNight
    Indicates that a service or location is operated, attended to, or provided specifically during nighttime hours.
  • E. nightServicePattern
    Indicates that a service or operation follows a specific pattern or schedule that applies only during nighttime hours.
  • 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_69e2fac597708190a922bf39a49ec70a completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f65f7731e4819099d5bd3d915ee266 completed May 2, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f65c1f94ac8190bc6fbc7916fc0d82 completed May 2, 2026, 8:18 p.m.
Created at: April 18, 2026, 5:26 a.m.