Triple
T3241762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-train network |
E67978
|
entity |
| Predicate | offPeakFrequency |
P85
|
FINISHED |
| Object | typically 10 minutes on main lines |
—
|
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: typically 10 minutes on main lines | Statement: [S-train network, offPeakFrequency, typically 10 minutes on main lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offPeakFrequency Context triple: [S-train network, offPeakFrequency, typically 10 minutes on main lines]
-
A.
offPeakServicePattern
Indicates the service pattern or schedule that applies during off-peak (non-rush-hour) times.
-
B.
populationPeakPeriod
Indicates the time period during which a population reached its highest recorded level.
-
C.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
D.
usagePeak
Indicates that the usage or consumption of something reaches its highest level or intensity during a particular time or condition.
-
E.
frequency
chosen
Indicates how often an event, action, or relationship occurs within a given period or context.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaef76d908190815bb456e366ee0a |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.