Triple
T37580564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 103rd Street (IND Eighth Avenue Line) |
E934943
|
entity |
| Predicate | servedByLocalService |
P29056
|
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: [103rd Street (IND Eighth Avenue Line), servedByLocalService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByLocalService Context triple: [103rd Street (IND Eighth Avenue Line), servedByLocalService, yes]
-
A.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
B.
hasLocalService
chosen
Indicates that one entity provides or is associated with a service that operates within the local area or vicinity of another entity.
-
C.
governedForLocalServicesBy
Indicates that an entity’s local services are administered, managed, or overseen by a specified governing authority or body.
-
D.
servedByServiceVia
Indicates that something receives service or is fulfilled through a specific service acting as the intermediary or delivery mechanism.
-
E.
servedByPort
Indicates that something (such as a service, route, or connection) is provided or made accessible through a particular port.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00776c4ebc8190899005fda34234d5 |
completed | May 10, 2026, 12:17 p.m. |
| PD | Predicate disambiguation | batch_6a0076f8a4c4819093ed577e67aa38f9 |
completed | May 10, 2026, 12:15 p.m. |
Created at: May 3, 2026, 4:17 p.m.