Triple
T7565459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitchburg Line |
E178900
|
entity |
| Predicate | hasPeakDirectionService |
P77639
|
FINISHED |
| Object | toward Boston in morning |
—
|
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: toward Boston in morning | Statement: [Fitchburg Line, hasPeakDirectionService, toward Boston in morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakDirectionService Context triple: [Fitchburg Line, hasPeakDirectionService, toward Boston in morning]
-
A.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
B.
hasPeakHourService
Indicates that a service operates or is available during designated peak or high-demand hours.
-
C.
hasPeakUsageInHemisphere
Indicates that the time period of highest usage or activity for something occurs within a specified hemisphere (e.g., Northern or Southern).
-
D.
hasHigherPeaksNearby
Indicates that an entity is located near other entities whose peak elevations are higher than its own.
-
E.
hasNearbyPeak
Indicates that one location has another peak situated close to it in geographic space.
- F. None of above. chosen
Provenance (4 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8fde87c81909795fc713d7378ff |
completed | March 27, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69c6f4dc485c819080da13e3b7f4f08f |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f59517648190ac0a9e9cba045dd5 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:50 p.m.