Triple

T28887082
Position Surface form Disambiguated ID Type / Status
Subject Northern line Edgware branch (via Camden Town) E732595 entity
Predicate hasPeakHourCrowding P35231 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: [Northern line Edgware branch (via Camden Town), hasPeakHourCrowding, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPeakHourCrowding
Context triple: [Northern line Edgware branch (via Camden Town), hasPeakHourCrowding, yes]
  • A. hasPeakHourService
    Indicates that a service operates or is available during designated peak or high-demand hours.
  • B. hasPeakHourFrequency
    Indicates how often a service or event occurs during designated peak hours.
  • C. hasHeavyPassengerTraffic chosen
    Indicates that an entity experiences a high volume of passenger movement or usage over a given period.
  • D. hasPeakHourFunction
    Indicates that something performs a specific role or behavior during peak hours of activity or usage.
  • E. hasNumberOfSeatsAtPeak
    Indicates the maximum number of seats available or occupied at the peak usage or capacity of something.
  • 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_69f05b07bdec819080cadfe147aa1f25 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f78c61ed4c8190ad84c918fa9af55a completed May 3, 2026, 5:56 p.m.
PD Predicate disambiguation batch_69f78b8cb3a881909ebaac1b503988c2 completed May 3, 2026, 5:53 p.m.
Created at: April 28, 2026, 7:51 a.m.