Triple
T25777508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashby Canal |
E649192
|
entity |
| Predicate | partiallyClosedDueTo |
P153682
|
FINISHED |
| Object | mining subsidence |
—
|
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: mining subsidence | Statement: [Ashby Canal, partiallyClosedDueTo, mining subsidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyClosedDueTo Context triple: [Ashby Canal, partiallyClosedDueTo, mining subsidence]
-
A.
partiallyClosed
chosen
Indicates that something is not fully closed, but also not fully open, occupying an intermediate state of closure.
-
B.
reopenedPartially
Indicates that an entity that was previously closed or inactive has been opened again, but only to a limited or incomplete extent.
-
C.
partiallyReleased
Indicates that an entity has been released to some extent but not yet fully or completely released.
-
D.
partiallyCompleted
Indicates that an action, process, or task has been started and progressed to some extent, but has not yet been fully completed.
-
E.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 22, 2026, 5:35 a.m.