Triple
T8417018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delaware and Raritan Canal |
E198751
|
entity |
| Predicate | closedForCommercialTraffic |
P62921
|
FINISHED |
| Object | 1932 |
—
|
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: 1932 | Statement: [Delaware and Raritan Canal, closedForCommercialTraffic, 1932]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedForCommercialTraffic Context triple: [Delaware and Raritan Canal, closedForCommercialTraffic, 1932]
-
A.
closedToCommercialTrafficDate
chosen
Indicates the date on which something (typically a route, facility, or area) was officially closed to commercial traffic.
-
B.
closedToCivilianTraffic
Indicates that access along a route or at a location is restricted so that civilian vehicles or pedestrians are not allowed to use it.
-
C.
closedToThroughTraffic
Indicates that a route or area is not accessible for general passage and cannot be used as a through route for traffic.
-
D.
closedForPassengers
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
E.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c66b5c8190b9515f55dc08ac03 |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.