Triple
T7791264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairmount Line |
E180183
|
entity |
| Predicate | commuterRailZone |
P17300
|
FINISHED |
| Object | Zone 1A |
—
|
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: Zone 1A | Statement: [Fairmount Line, commuterRailZone, Zone 1A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commuterRailZone Context triple: [Fairmount Line, commuterRailZone, Zone 1A]
-
A.
commuterRailMode
Indicates that the relationship involves travel or transportation specifically by commuter rail as the mode of transit between the related entities.
-
B.
publicTransportZone
chosen
Indicates that an entity is located within, associated with, or valid for a specific public transportation fare or service zone.
-
C.
railwayZoneNumber
Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
-
D.
hasRailwayZone
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
-
E.
railAccessModel
Indicates the type or pattern of how rail infrastructure or services are accessed or connected between locations or entities.
- 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:30 p.m.