Triple
T27489361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairmount Corridor |
E693836
|
entity |
| Predicate | followsRailService |
P104377
|
FINISHED |
| Object | Fairmount Line commuter rail |
—
|
NE NERFINISHED |
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: Fairmount Line commuter rail | Statement: [Fairmount Corridor, followsRailService, Fairmount Line commuter rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsRailService Context triple: [Fairmount Corridor, followsRailService, Fairmount Line commuter rail]
-
A.
followsRailroad
Indicates that one entity is aligned with or travels along the path defined by a railroad.
-
B.
isRailServiceOf
chosen
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
C.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
-
D.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
E.
hasAdjacentRailService
Indicates that one location has rail service situated directly next to or immediately bordering it.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 1:04 p.m.