Triple
T1685036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMT Jamaica Line |
E36422
|
entity |
| Predicate | servesTrainType |
P21523
|
FINISHED |
| Object | lettered services |
—
|
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: lettered services | Statement: [BMT Jamaica Line, servesTrainType, lettered services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesTrainType Context triple: [BMT Jamaica Line, servesTrainType, lettered services]
-
A.
railServiceType
chosen
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
B.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
C.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
D.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
E.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.