Triple

T38312037
Position Surface form Disambiguated ID Type / Status
Subject Los Angeles Metro Rail D Line stations E1033713 entity
Predicate offPeakServiceHeadway P114667 FINISHED
Object approximately 12–20 minutes (typical planning value) 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: approximately 12–20 minutes (typical planning value) | Statement: [Los Angeles Metro Rail D Line stations, offPeakServiceHeadway, approximately 12–20 minutes (typical planning value)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offPeakServiceHeadway
Context triple: [Los Angeles Metro Rail D Line stations, offPeakServiceHeadway, approximately 12–20 minutes (typical planning value)]
  • A. offPeakServiceFrequency_minutes chosen
    Indicates the number of minutes between successive services during off-peak periods.
  • B. offPeakServicePattern
    Indicates the service pattern or schedule that applies during off-peak (non-rush-hour) times.
  • C. typicalOffPeakServiceTo
    Indicates the usual or standard off-peak (non-peak time) service pattern that operates to a given destination.
  • D. peakHours
    Indicates that an action, event, or condition occurs during the busiest or most heavily trafficked time period.
  • E. transitFrequencyApprox
    Indicates an approximate rate or regularity with which a transit event or service occurs between entities.
  • 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_69f76e132c408190969b3d35c04b87ae completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fccbd826708190b5fab12c4236299a completed May 7, 2026, 5:28 p.m.
PD Predicate disambiguation batch_69fcc58838e08190b8fa54aa5c165f2d completed May 7, 2026, 5:02 p.m.
Created at: May 3, 2026, 4:30 p.m.