Triple
T37580565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 103rd Street (IND Eighth Avenue Line) |
E934943
|
entity |
| Predicate | servedByExpressService |
P202382
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [103rd Street (IND Eighth Avenue Line), servedByExpressService, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByExpressService Context triple: [103rd Street (IND Eighth Avenue Line), servedByExpressService, no]
-
A.
canBeExpress
Indicates that one entity is capable of being represented, articulated, or conveyed in the form of another entity or medium.
-
B.
primaryExpressService
Indicates that an entity provides or is associated with the main, prioritized express-level service in a given context.
-
C.
hasUPExpressService
Indicates that a location or entity is served by the UP Express (Union Pearson Express) transit service.
-
D.
servesCarrier
Indicates that one entity provides carrier services or functions as a carrier on behalf of another entity.
-
E.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
- F. None of above. chosen
Provenance (4 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00781b749c8190921c46e110cae0b0 |
completed | May 10, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_6a0077df3c8481909fabc9e84f5936e3 |
completed | May 10, 2026, 12:19 p.m. |
| PDg | Predicate description generation | batch_6a00781ac0f48190a77e2c326a4d6693 |
completed | May 10, 2026, 12:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.