Triple
T21015163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salts Mill |
E517653
|
entity |
| Predicate | industrialClosure |
P130772
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Salts Mill, industrialClosure, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industrialClosure Context triple: [Salts Mill, industrialClosure, 1980s]
-
A.
closedAsIndustrialFacility
chosen
Indicates that an entity ceased operations specifically in its role as an industrial facility.
-
B.
plantClosureRelatedTo
Indicates that a plant’s closure is connected or associated with a specified cause, factor, event, or entity.
-
C.
industrialCategory
Indicates the industry or sector classification to which an entity (such as a business or organization) belongs.
-
D.
industrialUseEnd
Indicates the point in time or condition at which an industrial use or application of something is terminated or ceases.
-
E.
industrialFocus
Indicates a relationship where an entity is primarily concerned with, specialized in, or directed toward a particular industrial sector or area of industrial activity.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc58272881908a61eda7755ed332 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:54 p.m.