Triple
T16238403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chesapeake Beach Railway |
E394175
|
entity |
| Predicate | beganRegularService |
P35191
|
FINISHED |
| Object | 1899 |
—
|
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: 1899 | Statement: [Chesapeake Beach Railway, beganRegularService, 1899]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganRegularService Context triple: [Chesapeake Beach Railway, beganRegularService, 1899]
-
A.
openedForCommercialService
chosen
Indicates that something (such as a facility, route, or service) began operating and became available for regular commercial use.
-
B.
openedForServiceTo
Indicates that one entity has been made available or activated to provide service or functionality to another entity.
-
C.
began
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
D.
permanentServiceBegan
Indicates that an entity’s ongoing or long-term service or role officially started at a specific point in time.
-
E.
commuterServiceBegan
Indicates that a commuter transportation service was initiated or began operating between specified locations or entities.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455c7a3c81909e3b42edf03be43e |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.