Triple
T32537837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitby–Pickering line |
E831637
|
entity |
| Predicate | closedAsPartOf |
P183527
|
FINISHED |
| Object | Beeching cuts |
—
|
NE NERFINISHED |
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: Beeching cuts | Statement: [Whitby–Pickering line, closedAsPartOf, Beeching cuts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closedAsPartOf Context triple: [Whitby–Pickering line, closedAsPartOf, Beeching cuts]
-
A.
closedAs
Indicates that one entity has been brought to an end, resolved, or made no longer active as a result of another entity or action.
-
B.
closedBy
Indicates that one entity performs the action of closing, finishing, or terminating another entity (such as a task, issue, or process).
-
C.
closedIn
Indicates that one entity is enclosed, contained, or surrounded within the boundaries or limits defined by another entity.
-
D.
closedUnder
Indicates that applying a specified operation to elements within a set always produces a result that is also an element of that same set.
-
E.
closedAsMine
Indicates that an issue or report was closed because it was determined to be a duplicate of one already owned or previously handled by the closer.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 1, 2026, 1:01 a.m.