Triple
T4779213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinchliffe Stadium |
E106130
|
entity |
| Predicate | conditionAfterClosure |
P59269
|
FINISHED |
| Object | deteriorated |
—
|
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: deteriorated | Statement: [Hinchliffe Stadium, conditionAfterClosure, deteriorated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionAfterClosure Context triple: [Hinchliffe Stadium, conditionAfterClosure, deteriorated]
-
A.
subjectToClosure
Indicates that an entity is liable or scheduled to be closed, discontinued, or shut down under certain conditions or plans.
-
B.
closureAffected
Indicates that an entity is impacted or influenced by the closing or termination of another entity, process, or resource.
-
C.
closureCompleted
Indicates that a previously initiated closure process or shutdown has been fully and successfully completed.
-
D.
closureProcess
Indicates the procedure or set of actions carried out to formally conclude, finalize, or terminate an ongoing activity, case, or process.
-
E.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6922407481908565ed0b1dac2b30 |
completed | March 20, 2026, 3:34 p.m. |
Created at: March 20, 2026, 1:21 p.m.