Triple
T5221133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fife coalfield |
E117869
|
entity |
| Predicate | closureTrend |
P62108
|
FINISHED |
| Object | progressive pit closures in late 20th century |
—
|
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: progressive pit closures in late 20th century | Statement: [Fife coalfield, closureTrend, progressive pit closures in late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closureTrend Context triple: [Fife coalfield, closureTrend, progressive pit closures in late 20th century]
-
A.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
-
B.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
C.
closureFrequency
Indicates how often a particular process, event, or entity is closed or brought to an end within a given period.
-
D.
closingStimulus
Indicates that one entity serves as the stimulus or trigger that causes another entity to close or become closed.
-
E.
closingContains
Indicates that one closing element, event, or period fully includes another within its temporal or structural bounds.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7ab846548190bcd2c5cd238f6cd9 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78a89b608190b259d3d8658f8f7c |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:48 p.m.