Triple
T24553333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concord Junction |
E607434
|
entity |
| Predicate | servedTodayBy |
P56872
|
FINISHED |
| Object | MBTA Commuter Rail Fitchburg Line |
—
|
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: MBTA Commuter Rail Fitchburg Line | Statement: [Concord Junction, servedTodayBy, MBTA Commuter Rail Fitchburg Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedTodayBy Context triple: [Concord Junction, servedTodayBy, MBTA Commuter Rail Fitchburg Line]
-
A.
servedDuring
Indicates that one entity held a role, position, or performed a function within the time period defined by another entity.
-
B.
presentlyServedBy
chosen
Indicates that an entity is currently being provided with service or attended to by another entity.
-
C.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
D.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
-
E.
servedBetween
Indicates that an entity provided service or operated during a time interval bounded by two specified temporal points.
- 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8cf1ef88190977da0fb79796616 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.