Triple
T6759423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Subway 6 line |
E154552
|
entity |
| Predicate | daytimeService |
P46476
|
FINISHED |
| Object | supplemented by <6> express service in the Bronx |
—
|
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: supplemented by <6> express service in the Bronx | Statement: [New York City Subway 6 line, daytimeService, supplemented by <6> express service in the Bronx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: daytimeService Context triple: [New York City Subway 6 line, daytimeService, supplemented by <6> express service in the Bronx]
-
A.
middayService
chosen
Indicates a service or activity that takes place around the middle of the day.
-
B.
hasDailyService
Indicates that a service or operation occurs every day on a regular, scheduled basis.
-
C.
dayPattern
Indicates the recurring schedule or configuration of days on which an event, action, or condition occurs.
-
D.
weekendService
Indicates that a service, operation, or activity is provided or occurs specifically on weekends.
-
E.
isDiurnal
Indicates that an entity is active during the daytime and rests at night.
- 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_69c6880fd5808190be684854081e27dd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:12 p.m.