Triple
T3166383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Subway B line |
E66220
|
entity |
| Predicate | middayService |
P46476
|
FINISHED |
| Object | operates between Bedford Park Boulevard and Brighton Beach |
—
|
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: operates between Bedford Park Boulevard and Brighton Beach | Statement: [New York City Subway B line, middayService, operates between Bedford Park Boulevard and Brighton Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: middayService Context triple: [New York City Subway B line, middayService, operates between Bedford Park Boulevard and Brighton Beach]
-
A.
servedDuring
Indicates that one entity held a role, position, or performed a function within the time period defined by another entity.
-
B.
hasDailyService
Indicates that a service or operation occurs every day on a regular, scheduled basis.
-
C.
weekendService
Indicates that a service, operation, or activity is provided or occurs specifically on weekends.
-
D.
budTime
Indicates the time or period when a bud forms or begins to develop.
-
E.
weekdayServicePattern
Indicates a service pattern or schedule that specifically applies on weekdays rather than weekends or holidays.
- 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada643e3e481908f4526d66e36e150 |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:06 p.m.