Triple
T12649848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRT Purple Line |
E302126
|
entity |
| Predicate | offPeakHeadway_minutes |
P20359
|
FINISHED |
| Object | approximately 6 to 10 |
—
|
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 6 to 10 | Statement: [MRT Purple Line, offPeakHeadway_minutes, approximately 6 to 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offPeakHeadway_minutes Context triple: [MRT Purple Line, offPeakHeadway_minutes, approximately 6 to 10]
-
A.
transitFrequencyApprox
chosen
Indicates an approximate rate or regularity with which a transit event or service occurs between entities.
-
B.
peakHours
Indicates that an action, event, or condition occurs during the busiest or most heavily trafficked time period.
-
C.
offPeakServicePattern
Indicates the service pattern or schedule that applies during off-peak (non-rush-hour) times.
-
D.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
E.
weekdayPeakDirectionService
Indicates that the service operates primarily during weekday peak travel periods in a specific direction.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:18 p.m.