Triple
T7622563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitchburg Line stations |
E172534
|
entity |
| Predicate | areServedBy |
P27768
|
FINISHED |
| Object | diesel locomotives |
—
|
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: diesel locomotives | Statement: [Fitchburg Line stations, areServedBy, diesel locomotives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areServedBy Context triple: [Fitchburg Line stations, areServedBy, diesel locomotives]
-
A.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
B.
servesOn
Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
-
C.
presentlyServedBy
Indicates that an entity is currently being provided with service or attended to by another entity.
-
D.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
-
E.
alsoServedBy
chosen
Indicates that the same service, function, or role is additionally provided or fulfilled by another entity alongside the primary one.
- 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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:56 p.m.