Triple
T27448318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morrison Avenue–Soundview |
E692354
|
entity |
| Predicate | servedByTime |
P137524
|
FINISHED |
| Object | all times (6 local) |
—
|
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: all times (6 local) | Statement: [Morrison Avenue–Soundview, servedByTime, all times (6 local)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByTime Context triple: [Morrison Avenue–Soundview, servedByTime, all times (6 local)]
-
A.
servedTimeFor
Indicates that one entity has completed or spent a specified duration of time serving a sentence, obligation, or term on behalf of another entity or for a particular case or offense.
-
B.
servedTimeAt
Indicates the specific time period during which an entity was served or received service at a particular place or context.
-
C.
servedByTimePeriod
chosen
Indicates that a service, event, or activity occurs or is provided during a specified time period.
-
D.
servedBetween
Indicates that an entity provided service or operated during a time interval bounded by two specified temporal points.
-
E.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
- 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 27, 2026, 12:46 p.m.