Triple
T5504709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danbury Branch |
E144410
|
entity |
| Predicate | openedForRailService |
P30642
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Danbury Branch, openedForRailService, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForRailService Context triple: [Danbury Branch, openedForRailService, 19th century]
-
A.
openedToRailTraffic
Indicates that a rail line, track, or related infrastructure has begun operating and is officially available for use by train traffic.
-
B.
openedAsRailStop
Indicates that an entity began operation or was first established specifically as a railway stop.
-
C.
openedForThroughService
Indicates that an entity has been made accessible or available specifically for use via a through-service connection or route, rather than as a standalone endpoint.
-
D.
railwayWorksOpened
Indicates that a railway facility, such as a station, line, or related infrastructure, was officially opened or began operation on a specified date.
-
E.
railwayLineOpened
chosen
Indicates that a railway line began official operation or service on a specified date.
- 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_69c008f6b5048190a09064116062cf69 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0d21848190ae8c41561eca6342 |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b07bde08190b3933b96bdc70dd5 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.