Triple
T5268010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedford Park Boulevard–Lehman College |
E119184
|
entity |
| Predicate | hasExpressTrack |
P26424
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bedford Park Boulevard–Lehman College, hasExpressTrack, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpressTrack Context triple: [Bedford Park Boulevard–Lehman College, hasExpressTrack, yes]
-
A.
hasExpressTracks
chosen
Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
-
B.
includesTrackingNumber
Indicates that something contains or provides a tracking number associated with it.
-
C.
primaryExpressService
Indicates that an entity provides or is associated with the main, prioritized express-level service in a given context.
-
D.
isOnFreightRoute
Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
-
E.
hasExpressSegments
Indicates that a route, service, or path includes segments that are designated as express, skipping certain intermediate stops or steps.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.