Triple
T8067376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Völklingen Ironworks |
E188276
|
entity |
| Predicate | ceasedIndustrialOperation |
P56576
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [Völklingen Ironworks, ceasedIndustrialOperation, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedIndustrialOperation Context triple: [Völklingen Ironworks, ceasedIndustrialOperation, 1986]
-
A.
ceasedOperation
Indicates that an entity has stopped functioning, operating, or carrying out its activities, typically in a permanent or indefinite manner.
-
B.
ceasedOperationsAs
Indicates that an entity stopped functioning or operating in a particular role, capacity, or status.
-
C.
industrialUseEnd
chosen
Indicates the point in time or condition at which an industrial use or application of something is terminated or ceases.
-
D.
hasIndustrialCompany
Indicates that one entity possesses, controls, or is associated with an industrial company.
-
E.
industrialCategory
Indicates the industry or sector classification to which an entity (such as a business or organization) belongs.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ff75d208190b7c53d2fe55878ac |
completed | March 31, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:26 p.m.