Triple
T16313499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glamorganshire Canal |
E396114
|
entity |
| Predicate | officialClosure |
P122648
|
FINISHED |
| Object | 1951 |
—
|
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: 1951 | Statement: [Glamorganshire Canal, officialClosure, 1951]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialClosure Context triple: [Glamorganshire Canal, officialClosure, 1951]
-
A.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
B.
closedFor
Indicates that an entity is not available or accessible for use, entry, or operation during a specified time, condition, or reason.
-
C.
closureType
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
D.
closedToPublic
Indicates that access to the referenced entity is restricted so that the general public is not allowed to enter or use it.
-
E.
closedOffFrom
Indicates that one entity is isolated, blocked, or prevented from accessing, interacting with, or being influenced by another entity.
- 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_69d87f23bb088190a16fbb91a1957ea5 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288dd90d4819097bd01a7b40a54cd |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.