Triple
T5372406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Settle–Carlisle line |
E108880
|
entity |
| Predicate | savedFromClosure |
P63609
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Settle–Carlisle line, savedFromClosure, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: savedFromClosure Context triple: [Settle–Carlisle line, savedFromClosure, 1989]
-
A.
closureAffected
Indicates that an entity is impacted or influenced by the closing or termination of another entity, process, or resource.
-
B.
temporaryClosure
Indicates that an entity is closed or unavailable for a limited, non-permanent period of time.
-
C.
closureContext
Indicates the surrounding scope or environment in which an operation, expression, or function is defined and executed, capturing the variables and bindings available to it.
-
D.
subjectToClosure
Indicates that an entity is liable or scheduled to be closed, discontinued, or shut down under certain conditions or plans.
-
E.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd887f5b0081909456992d1a071928 |
completed | March 20, 2026, 5:48 p.m. |
Created at: March 20, 2026, 2:02 p.m.