Triple
T1327260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metra Milwaukee District West Line |
E28356
|
entity |
| Predicate | peakDirectionService |
P12959
|
FINISHED |
| Object | inbound to Chicago in morning peak |
—
|
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: inbound to Chicago in morning peak | Statement: [Metra Milwaukee District West Line, peakDirectionService, inbound to Chicago in morning peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakDirectionService Context triple: [Metra Milwaukee District West Line, peakDirectionService, inbound to Chicago in morning peak]
-
A.
peakServiceOnly
Indicates that the service operates only during peak periods and is not available at off-peak times.
-
B.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
C.
powerDirection
Indicates the direction in which power, influence, or control flows from one entity to another.
-
D.
servesDirection
chosen
Indicates that one entity provides service or functionality oriented toward, or in the direction of, another entity.
-
E.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c0a22881909eff0fc6c91a5f41 |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.