Triple
T5382404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forth and Clyde Canal |
E113117
|
entity |
| Predicate | closedToCommercialTrafficDate |
P62921
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Forth and Clyde Canal, closedToCommercialTrafficDate, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedToCommercialTrafficDate Context triple: [Forth and Clyde Canal, closedToCommercialTrafficDate, 1960s]
-
A.
closedToThroughTraffic
Indicates that a route or area is not accessible for general passage and cannot be used as a through route for traffic.
-
B.
closedForPassengers
Indicates that a transportation facility or vehicle is not available for use by passengers.
-
C.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
D.
roadClosesIn
Indicates that a road becomes closed or inaccessible within a specified location, area, or boundary.
-
E.
closureYear
Indicates the year in which an entity (such as an organization, facility, or service) ceased operations or was officially closed.
- F. None of above. chosen
Provenance (4 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86d163f88190939638d44fcb24a7 |
completed | March 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd853005088190b1b092a9beb090b2 |
completed | March 20, 2026, 5:34 p.m. |
Created at: March 20, 2026, 2:03 p.m.