Triple
T3241761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-train network |
E67978
|
entity |
| Predicate | peakFrequency |
P85
|
FINISHED |
| Object | as low as 2–5 minutes on core sections |
—
|
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: as low as 2–5 minutes on core sections | Statement: [S-train network, peakFrequency, as low as 2–5 minutes on core sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakFrequency Context triple: [S-train network, peakFrequency, as low as 2–5 minutes on core sections]
-
A.
peakUse
Indicates the time, condition, or context in which something reaches its maximum level of use or intensity.
-
B.
frequency
chosen
Indicates how often an event, action, or relationship occurs within a given period or context.
-
C.
peakType
Indicates the specific classification or category of a peak based on its form, prominence, or other defining characteristics.
-
D.
frequencyDependsOn
Indicates that the frequency of one event, action, or state is determined or influenced by another factor or condition.
-
E.
frequencyChange
Indicates a change in how often an event, action, or state occurs over time.
- 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.