Triple
T20394229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryton, United Kingdom |
E500157
|
entity |
| Predicate | plantClosure |
P43843
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Ryton, United Kingdom, plantClosure, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantClosure Context triple: [Ryton, United Kingdom, plantClosure, 2007]
-
A.
openPitClosedIn
Indicates that an open-pit mine or excavation has been closed, decommissioned, or otherwise taken out of active use at a specified time or under specified conditions.
-
B.
restaurantClosureDate
Indicates the date on which a restaurant ceases or ceased operations, marking its official closure.
-
C.
closedCityDuring
Indicates that a city is not accessible or operational during a specified time period or interval.
-
D.
closingLocation
Indicates the place or venue where an event, process, or activity comes to an end or is formally concluded.
-
E.
announcedPermanentClosure
chosen
Indicates that an entity has formally stated that it will cease operations or availability indefinitely and not reopen.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e679122058819083e3615a5ea0a82e |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.