Triple
T3009950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitefield Metrolink stop |
E82191
|
entity |
| Predicate | hasTramFrequencyWeekdayPeak |
P20359
|
FINISHED |
| Object | every 6 minutes |
—
|
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: every 6 minutes | Statement: [Whitefield Metrolink stop, hasTramFrequencyWeekdayPeak, every 6 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTramFrequencyWeekdayPeak Context triple: [Whitefield Metrolink stop, hasTramFrequencyWeekdayPeak, every 6 minutes]
-
A.
peakDailyTrains
Indicates the maximum number of trains operating per day on a given route, line, or segment during its busiest period.
-
B.
weekdayPeakDirectionService
Indicates that the service operates primarily during weekday peak travel periods in a specific direction.
-
C.
transitFrequencyApprox
chosen
Indicates an approximate rate or regularity with which a transit event or service occurs between entities.
-
D.
dailyRidershipPeak
Indicates that the relationship specifies the highest number of riders or users recorded for a service or system within a single day.
-
E.
hasTramway
Indicates that a location or area is served by, contains, or is connected to a tramway system.
- 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_69ad8b1eb53481908c39bbcd1ec104b2 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a4ccbf08190a7580c9e758804d0 |
completed | March 8, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.